fix(release): create local v<version> tag before changesets/action pushes#6
Merged
Merged
Conversation
…shes changesets/action@v1 shells out `git push origin v<version>` for single-package repos and does not create the tag itself; `changeset publish` would have, but our custom publish script replaced it. Add `git tag v<version>` here, and fix the gh-release skip-check to look up the correct release name (`v<version>`, not `<pkg>@<version>`). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
resumex | 17b93cb | Commit Preview URL Branch Preview URL |
May 01 2026, 10:04 PM |
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.
Summary
error: src refspec v0.1.0 does not match anybecausescripts/release-tag.mjsemittedNew tag: resumex@0.1.0to signalchangesets/action@v1but never created the local tag.changesets/action@v1ignores the package name in theNew tag:line and shells outgit push origin v${version}(src/run.ts:142-149,src/git.ts:78-92). It does not create the tag itself —changeset publishwould have, but we replaced that flow with our custom script.v${version}tag before emitting the line, and correct thegh release viewskip-check to usev${version}(the action creates releases atv${version}, not<pkg>@<version>), so re-runs are actually no-ops.Test plan
v0.1.0, creates the GitHub Release with the CHANGELOG body.