Merged
Conversation
Adds a skill that covers the full release flow: picking the next version, tagging and pushing, waiting for the Release Binaries CI workflow to create the GitHub release, then drafting and publishing release notes. Complements the existing release-notes skill, which remains the notes-only flow for updating an already-published release.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Adds a
releaseskill at.agents/skills/release/SKILL.mdthat covers the full release flow:git tag v…and push to originRelease Binariesworkflow (build.yml) to build darwin/linux × amd64/arm64 binaries and auto-create the GitHub releaserelease-notesskill for tone, structure, and categoriesgh release editon the release the workflow already createdWhy both skills
release-notesstays focused on the notes-only flow — useful when a release already exists and only the notes need updating/rewriting.releaseorchestrates the whole thing for the common case where you're cutting a new version from scratch.Key invariants documented
gh release create(CI already creates the release; manual calls would race)