feat(ci): add release version validation to prevent mismatched releases#736
Merged
meryldakin merged 1 commit intomainfrom Mar 13, 2026
Merged
feat(ci): add release version validation to prevent mismatched releases#736meryldakin merged 1 commit intomainfrom
meryldakin merged 1 commit intomainfrom
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
- Add validate-release job that compares git tag to package.json version - Block publish-brew and publish-npm if versions don't match - Provide clear error message with remediation steps - Add Claude skill for guided release process
meryldakin
force-pushed
the
add-release-validation
branch
from
ab9b145 to
e40bdd8
Compare
andy-knock
approved these changes
Mar 12, 2026
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
2 participants
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
Adds validation to the release pipeline to prevent version mismatches that cause failed releases.
How it works
When a release is created, the new
validate-releasejob runs first:v1.0.2→1.0.2)package.jsonpublish-brewandpublish-npmto proceed