Release Tool: Create GitHub Release via gh release create - #4
Merged
Merged
Conversation
…reate gh skill publish --tag refuses tags that already exist on the remote, because it creates the tag itself from the branch head. The release tool pushes the annotated tag atomically with main first, so publishing failed with "tag 2.0.0 already exists". Create the release for the existing tag with gh release create --verify-tag --generate-notes instead; gh skill publish --dry-run still validates the skills. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-skills topic - Pass the version's CHANGELOG.md section to gh release create via --notes-file instead of generating notes from pull request titles. - Check the agent-skills topic with gh repo view before releasing, since gh skill publish no longer does. - Advise running gh release view before retrying a failed publish. - Point the README's manual publishing advice to gh release create --verify-tag. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
feO2x
changed the title
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.
Problem
Release run 1 failed after pushing
mainand2.0.0:gh skill publish --tag Xfetches the remote tags, refusesXif it already exists, and then creates the tag itself on the server through the releases API (target_commitish= current branch). The release tool pushes the annotated tag together withmainfirst, sogh skill publish --tagcan never succeed. The recovery hint it printed (gh skill publish --tag 2.0.0) fails the same way.Fix
gh release create <tag> --verify-tag --generate-notes.--verify-tagstops the command if the tag isn't on the remote, so it never creates one.gh skill publishdid in non-interactive mode is lost:gh skill publish --dry-runstill validates the skills before the release commit, and the repository already has theagent-skillstopic.README.md, andAGENTS.mdto match.Keeping the atomic push means
mainand the tag reach the remote together or not at all, the tag stays annotated, and it points exactly at the validated commit.This uses
build:because the release tool isn't shipped to users, so no release is triggered.Follow-up
2.0.0 has a tag but no GitHub Release yet. After merging, create it with:
Testing
dotnet test: 146 passed🤖 Generated with Claude Code