Skip to content

CHANGELOG: 1.0.1 - #87

Merged
apostasie merged 1 commit into
mainfrom
claudio/20261004-release-1.0.1
Oct 5, 2026
Merged

apostasie merged 1 commit into
mainfrom
claudio/20261004-release-1.0.1

Conversation

@closer-claudio

Copy link
Copy Markdown

🎯 Why: release train wave 1 (Manager, for @apostasie). xz is to be tagged v1.0.1.

🛠️ What: CHANGELOG.md's Unreleased entries become the [1.0.1] section, dated 2026-10-05.

🧪 How:

  1. CHANGELOG: 1.0.1. V: go doc -all of every non-internal package at v1.0.0 and at main shows no exported API change (blake3: parameter-list formatting only), so patch. The commits since v1.0.0 are lint alignment, tooling and the entries listed. just lint (every lane but links) and just test green locally. U: links (sandbox).

📝 The date is the day the tag is expected; if the tag lands later, change the heading's date in the same edit.

The unreleased changes since 1.0.0 become the 1.0.1 section, dated for
the release. The exported API is unchanged since v1.0.0, so it is a
patch release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: closer-claudio <claudio@farcloser.world>

@closer-claudio closer-claudio left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Ready at 788c49d: the Unreleased entries become [1.0.1] - 2026-10-05, the train's xz tag; 12/12 checks green including the gate.

🔍 Verified last: diff read at 788c49d, one heading. The section holds the one Fixed entry, the (0, nil) retry from #86. Patch level holds: go doc -all of the three non-internal packages at v1.0.0 and at main gives the same 88 exported declaration lines, so nothing in the API moved; the 150-odd commits since v1.0.0 are lint alignment, tooling and that fix. Body in #217's shape.

@apostasie
apostasie merged commit fc83cbd into main Oct 5, 2026
12 checks passed
@apostasie
apostasie deleted the claudio/20261004-release-1.0.1 branch October 5, 2026 06:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants