fix: restore ## Unreleased, which the #224 merge turned into a duplicate v0.149.1 - #225
Merged
Merged
Conversation
…ate v0.149.1 Merging #224 renamed its ## Unreleased section to ## v0.149.1, but that heading already existed: commit 011556d ("release v0.149.1") had renamed the section for the sibling change in #222, and tag v0.149.1 points at it. The result on master was two ## v0.149.1 headings, this branch's bullets under the first, and no ## Unreleased section at all. Because the release watcher keys on ## Unreleased, it reported reason=no-release-files and skipped the repo — so this change would never have been released. Repair direction is decided by the tag, not by where the merge put the entry: git tag --contains cd3f495 returns nothing, so this work is in no tag and its bullets move back under ## Unreleased. The sibling's section stays where its tag put it. Verified: one ## v0.149.1 heading remains, this branch's two bullets sit under ## Unreleased, the sibling's bullet sits under ## v0.149.1, and the fold guard prints only '-## v0.149.1' / '+## Unreleased'.
There was a problem hiding this comment.
Selector Mode Review — bborbe/vault-cli PR #225
Changed files: CHANGELOG.md (1 file)
The diff restores ## Unreleased at the top of the changelog, undoing a duplicate ## v0.149.1 that the #224 merge introduced. The two bullets (remove-metrics-session feat, task-auditor goal-link fix) are now correctly under ## Unreleased with ## v0.149.1 below as the last released version.
No code changes — this is a documentation-only bugfix. The mechanical funnel found nothing (0 findings). No agents are applicable.
Version alignment check (CLAUDE.md MANDATORY):
CHANGELOG.mdtop entry:## Unreleased✓.claude-plugin/plugin.jsonversion: v0.149.1 (unchanged, this PR doesn't bump it).claude-plugin/marketplace.jsonversion: v0.149.1 (unchanged)
No version fields changed in this PR — correct, since this is a pure changelog restore.
Plan concerns: Empty — no concerns were raised.
{
"verdict": "approve",
"summary": "Trivial but necessary changelog fix: the #224 merge accidentally duplicated the v0.149.1 section header, and this PR restores ## Unreleased as the top section. No code changes.",
"comments": [],
"concerns_addressed": []
}
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
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.
One-line repair: restores
## Unreleased, which the #224 merge turned into a second## v0.149.1heading.What went wrong
011556d release v0.149.1renamed## Unreleased→## v0.149.1for the change in #222, and tagv0.149.1points at it.#224 was branched before that release commit, so GitHub's merge had to reconcile two edits to the same region: theirs renamed the section, mine added bullets under it. The merge renamed mine too, and master ended up with:
Two consequences, both silent:
## Unreleasedsection existed. The release watcher keys on it, so it reportedreason=no-release-filesand skipped the repo — feat: add task remove-metrics-session and stop the auditor contradicting itself #224's change would never have been released.git tag --contains cd3f4953returns nothing, so the work under the first heading is in no tag while wearing a released version's name.The repair
Repair direction is decided by the tag, not by where the merge put the entry.
git tag --contains cd3f4953is empty → this work is in no tag → its bullets move back under## Unreleased. The sibling's section stays where its tag put it.Verification
## v0.149.1heading remains.git diff origin/master -- CHANGELOG.md | grep -E '^[-+]## 'prints only-## v0.149.1/+## Unreleased.awkconfirms feat: add task remove-metrics-session and stop the auditor contradicting itself #224's two bullets sit under## Unreleasedand fix(task-auditor): note a deliberately-framed non-advancing goal link as MINOR #222's bullet sits under## v0.149.1.Merging this should let the release watcher pick the repo up again and cut the next patch.