chore(release): promote spec/016 to [2.0.0] for the v2.0.0 tag#29
Merged
Conversation
PR #28 was merged before its [Unreleased] → [2.0.0] CHANGELOG promotion landed, so master ended up with the spec/016 bullet still in [Unreleased] and no `## [2.0.0]` section to anchor the v2.0.0 tag. The post-merge release pipeline grep for `## [2.0.0]` failed and the tag was never cut. This release-prep PR closes the gap: - Move the spec/016 Changed bullet from the machine-managed [Unreleased] block into a new `## [2.0.0] - 2026-05-03` section (the release date is when the tag is cut, not when the content landed in master). - Empty the [Unreleased] block back to just its markers, matching the rendered output once the consumed fragment is removed. - Delete `changes/016-source-repository-layout.md` per the fragment lifecycle: "Release tagged and published — Delete the fragment" (we're tagging now; the [2.0.0] CHANGELOG entry is the durable record of the change). - Add `changes/release-v2.0.0.md` with `release_preparation: true` so `core-ops-release validate --base-ref master` accepts the metadata-only no-op-version-bump diff. The rendering tool excludes preparation-flagged fragments from [Unreleased] output, so the empty markers stay empty. Verification: - `cargo run --bin core-ops-release -- validate --base-ref master` Outcome: passed (Classification: exempt, Metadata-only: yes, CHANGELOG aligned: yes). - `cargo build --tests` + `cargo clippy --all-targets -- -D warnings` both clean (no source changes). After merge, tag v2.0.0 against the merge commit; CI publishes the GitHub Release using the new [2.0.0] section as release notes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
[Unreleased]→[2.0.0]CHANGELOG promotion landed, so master ended up with the spec/016 bullet still in[Unreleased]and no## [2.0.0]section. The post-merge release pipeline grep for## [2.0.0]failed and v2.0.0 was never tagged.## [2.0.0] - 2026-05-03section, empties[Unreleased]back to its markers, deletes the consumedchanges/016-source-repository-layout.mdper the fragment lifecycle, and adds arelease_preparation: truefragment socore-ops-release validateaccepts the metadata-only diff.Test plan
cargo run --bin core-ops-release -- validate --base-ref master— passed (Classification: exempt, Metadata-only: yes, CHANGELOG aligned: yes)cargo build --tests+cargo clippy --all-targets -- -D warnings— clean (no source changes)ci.ymlgreen on PR headv2.0.0against the merge commit; CI publishes the GitHub Release using the new[2.0.0]section as release noteschanges/release-v2.0.0.md(it's the prep fragment for THIS release; consumed once tagged)🤖 Generated with Claude Code