Conversation
package.json (0.1.0) had drifted from the released tag (v1.0.0) and nothing kept them in sync — release.yml took the version solely from a manual dispatch input and never touched package.json. - Bump package.json to 1.0.0 to match the existing v1.0.0 tag. - Drop the free-text version dispatch input; derive the tag from package.json. - Validate the derived tag against vX.Y.Z and fail fast otherwise. - Make tag-and-release idempotent: skip cleanly if the release already exists. - release-pr derives the version for its PR title from package.json too. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ci: make package.json the single source of truth for release version
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.
Automated release PR promoting
developtomain. Deployed commit: 6814667.