Repository navigation
chore(release): pin the next release to 5.12 - #1037
Merged
Merged
Conversation
The telemetry rewrite carries a breaking change that would bump the umbrella and six packages to a major. Pin each affected package to its next minor for this one release. Remove the pins once main is back-merged into next. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
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 & why
The telemetry rewrite (#993) carries a
BREAKING CHANGE:footer. Left alone, release-please bumps the umbrella and five packages to a major. This pins each affected package to its next minor for one release.🛠️ How it works
Adds
release-asto the six packages release-please would bump to a major: the root,aidd-dev,aidd-pm,aidd-orchestrator,aidd-telemetryandcli. The commit history is untouched:nextforbids force-push, and a rewrite would change five commit SHAs.🧪 How to verify
release-please release-pr --dry-run --target-branch chore/release-as-5-12proposes: root 5.12.0, aidd-dev 2.7.0, aidd-pm 2.6.0, aidd-orchestrator 2.4.0, aidd-telemetry 0.3.0, cli 5.5.0. Without this change, the same dry run onnextproposes 6.0.0, 3.0.0, 3.0.0, 3.0.0, 1.0.0 and 6.0.0.The pins must be removed from
release-please-config.jsononnextoncemainis back-merged, or every later release stays on these versions. The changelogs still list the breaking change, on purpose.🤖 Generated with Claude Code