GitHub Release
Prepare a release pull request for a single-package repository from its tags, public changes and changelog.
npx skills add github/awesome-copilot@github-release What it does
A commit count tells a maintainer little about whether consumers need to change their code. GitHub Release compares the public surface with the last release before proposing a version and changelog.
What changes after install
- Identify the previous tag and scope the public diff.
- Propose a semantic version with reasons for review.
- Prepare a release PR and hand off tagging after merge.
Install
Run this command with Node.js 22.20 or later and select your agent in the Skills CLI.
npx skills add github/awesome-copilot@github-release Before using GitHub Release
- A clean single-package Git checkout, release history, git and an authenticated GitHub CLI with appropriate access.
Read the reviewed setup instructions for the selected workflow.
When to use it
- Classify consumer-visible changes for a version bump.
- Prepare a release branch and changelog for review.
When not to use it
- Coordinating separate version histories in a multi-package repository.
A worked example
Give the agent a library whose latest changes add a public option and refactor an internal cache. Identify the package’s public source directory. Ask for a proposed version and a changelog draft, then inspect which change consumers actually need to know about.
Troubleshooting
- Fetch tags if the previous version looks stale.
- If the public diff is empty, inspect the selected path.
- If repository rules block a push, keep the prepared changes and resolve the branch requirement with the maintainer.
How it chooses an approach
Use the tag and public diff as the starting point. An incompatible interface, an additive option and an internal fix can justify different version decisions even when their commit messages sound similar.
When to use another skill
- Finishing a Development Branch for integrating an ordinary development branch.
- Netlify Deploy for publishing a review site.
- Verification Before Completion for checking evidence before tagging.
What to check after it runs
Check the base tag, version and release PR. The documented handoff leaves tagging the merge commit and publishing the GitHub Release to the maintainer.
Related workflows
More in DevOps
- Finish a Branch — branch integration
- Netlify Deploy — Netlify preview deployments
- Git Worktrees — isolated workspaces
Related skills in other categories
FAQ
- Does opening the release PR publish the release?
- The upstream procedure ends with a handoff. After the PR merges, the maintainer tags the merge commit and publishes the release.
- How should an internal refactor affect the changelog?
- Inspect the public diff and consumer impact before assigning a version change or drafting a user-facing entry.