Release 1.0.0: changelog section and the plan's record - #36
Merged
Merged
Conversation
…decision CHANGELOG.md: the Unreleased section becomes 1.0.0 — 2026-10-01, with what the first stable release is and what still runs in a Max session afterwards (plan 8.8, the Windows half of 6.4, the unchecked zips of 6.5); from 1.0.0 a change to the class contract is a major version. PRODUCTION-PLAN.md records the maintainer's decision to tag 1.0.0 with 8.8 outstanding, and the sequencing follows. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014sfhCxUoBQmLNnYBSn1ozG
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Two documents, for the
v1.0.0tag that follows this merge:CHANGELOG.md's Unreleased section becomes 1.0.0 — 2026-10-01, anddocs/PRODUCTION-PLAN.mdrecords the decision to tag 1.0.0 with 8.8 (the Mac session) outstanding.Why
The tag has to point at a
mainwhose changelog names the release, and min reads the package version from the latest tag, so the tag comes after this merge. The plan had gated 1.0 on 8.8; the maintainer decided (2026-10-01) that the contract changes being merged (#35) is the gate, and that what 8.8 verifies in Max is behavior the Linux battery and the glue test already pin. The changelog says what the first stable release is and what still runs in a Max session afterwards: 8.8, the Windows half of 6.4, and the arm64 and Windows zips of 6.5. From 1.0.0, a change to the class contract is a major version.Verification
Documentation only; no code changes. CI runs regardless. Not run here: the release workflow itself, which the tag triggers — for a 1.0 tag it builds, tests and packages on the four runners and attaches the zips to a draft release (
release.yml: 0.x publishes as a pre-release, 1.0 and later stay drafts until signing credentials exist). Publishing the draft is a deliberate act by hand.Notes for the reviewer
🤖 Generated with Claude Code
https://claude.ai/code/session_014sfhCxUoBQmLNnYBSn1ozG
Generated by Claude Code