Skip to content

chore: anchor CHANGELOG with 5.0.0-rc.2 entry so ShipIt bumps to rc.3#245

Merged
dbrattli merged 1 commit intomainfrom
chore/anchor-changelog-rc2
Apr 16, 2026
Merged

chore: anchor CHANGELOG with 5.0.0-rc.2 entry so ShipIt bumps to rc.3#245
dbrattli merged 1 commit intomainfrom
chore/anchor-changelog-rc2

Conversation

@dbrattli
Copy link
Copy Markdown
Collaborator

Summary

Without a header in ShipIt's ## X.Y.Z - date format, ShipIt can't read the current version from CHANGELOG.md and falls back to 0.0.0, proposing chore: release Fable.Python@0.0.1-rc.1 instead of the expected 5.0.0-rc.3.

This seeds the changelog with a ShipIt-parseable entry for the last released version (Fable.Python 5.0.0-rc.2 on NuGet) so the next release lands on 5.0.0-rc.3.

Test plan

  • After merge, the ShipIt - Pull Request job proposes chore: release Fable.Python@5.0.0-rc.3
  • Merging that release PR publishes Fable.Python 5.0.0-rc.3 to NuGet

🤖 Generated with Claude Code

Without a header in ShipIt's '## X.Y.Z - date' format, ShipIt cannot
read the current version from CHANGELOG.md and falls back to 0.0.0,
proposing '0.0.1-rc.1' instead of the expected '5.0.0-rc.3'. Seed the
changelog with the last published version as a ShipIt-parseable entry
so the next release bumps correctly.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@dbrattli dbrattli merged commit 66e5676 into main Apr 16, 2026
2 checks passed
@dbrattli dbrattli deleted the chore/anchor-changelog-rc2 branch April 16, 2026 00:45
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.

1 participant