release
/release
Tag and release a new gcx version. Use when the user wants to cut a release, tag a version, run the release process, or says "release patch/minor/major".
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Tag and release a new gcx version. Use when the user wants to cut a release, tag a version, run the release process, or says "release patch/minor/major".
Triggers from the description
Original author description
Tag and release a new gcx version. Use when the user wants to cut a release, tag a version, run the release process, or says "release patch/minor/major".
How it works
- Customer communications
- Release
- Contribution handoff
SKILL.md preview
--- name: release description: Tag and release a new gcx version. Use when the user wants to cut a release, tag a version, run the release process, or says "release patch/minor/major". --- # Releasing gcx ## Customer communications For every major release, or minor release containing breaking changes, prepare customer communications as part of the release: - Use [grafana-product:whats-new](https://github.com/grafana/ai-kit/tree/main/plugins/grafana-product/skills/whats-new) for new or improved capabilities. - Use [grafana-product:whats-next](https://github.com/grafana/ai-kit/tree/main/plugins/grafana-product/skills/whats-next) for breaking changes, deprecations, removals, or disruptive behaviour changes. - If both apply, prepare separate entries. Before running the release command, review the changes since the previous release to identify the required entries. Inspect source PRs and compatibility changes rather than relying solely on commit prefixes or generated release notes. Reuse existing contributions where appropriate. Read the relevant upstream skill and its required references, using `gh` to retrieve them if they are not installed. Follow their content and formatting guidance, but override their advance-notice timing: prepare the content during the release, without requiring a 2–4 week lead time or delaying the release to create one. Describe the actual release timing; do not present an already available change as upcoming. Include affected users, exact before/after behaviour, and concrete migration instructions for breaking changes. Verify CMS metadata rather than treating a gcx version as a Grafana self-managed release version. ## Release Automated via `mise run tag`. Requires `claude` CLI; [`svu`](https://github.com/caarlos0/svu) comes from `mise install`. ```bash mise run tag -- patch # or minor, major ``` This generates a changelog entry (via Claude), updates `CHANGELOG.md` and `.release-notes.md`, and runs `mise run docs:refresh -- vX.Y.Z` to generate the CLI and configuration references from the current checkout with the upcoming version. It commits these changes together on a `release/vX.Y.Z` branch and pushes the branch. Then: 1. Open a PR (the script prints the exact command). Review the changelog and the generated changes to `docs/sources/cli-reference.md` and `docs/sources/configuration.md`, run the repository's required checks, and merge it. 2. After merge, tag the commit on main and push the tag: ```bash git checkout main && git pull git tag v0.X.Y git push origin v0.X.Y ``` The tag push triggers the GoReleaser workflow. If release code changes during review, rerun `mise run docs:refresh -- vX.Y.Z` with the upcoming version and commit the updated references to the same PR. Without a version argument, `mise run docs:refresh` uses the latest published stable release; use that only for standalone documentation updates. ## Contribution handoff Before declaring the release complete, report the required contributions' draft paths and CMS submission/publication status. If submission is outstanding, name the comms owner and remaining action; a local draft alone is not a submitted contribution. If no contribution is required, state why.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · grafana/gcx | 100 | Apache-2.0 |
| josephfung/curia | 100 | MIT |
| max-sixty/worktrunk | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| anthony-chaudhary/fak | 100 | Apache-2.0 |
| tractorjuice/arc-kit | 100 | MIT |
| drvoss/everything-copilot-cli | 100 | MIT |
| sma1lboy/rove | 100 | MIT |
Database snapshot: 13.11.2026 · package version e77388b4e3bc (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 96tag-release
Use when asked to tag or cut a patch, minor, or major release. - 100create-new-release
Create and push a new semver release tag. Asks for release type (patch/minor/major), validates commit exists on remote, bumps version, and pushes the tag. - 100release-cli
Release a new version of the pd CLI. Runs tests, bumps version, creates git tag, and pushes to remote. Use when releasing a new CLI version. - 100version-release
Use when bumping version, creating a release tag, or pushing a version tag. Triggers on "version up", "release", "tag push", "bump version". - 100nvidia-nemoclaw-maintainer-cut-release-tag
Cut a new semver release — bump all version strings via bump-version.ts, open a release PR, and after merge tag main and push. Use when cutting a release, tagging a version, shipping a build, or preparing a deployment. Trigger keywords - cut tag, release tag, new tag, cut… - 100release-engineering
Version, changelog, tag, and publish a release. Use when cutting a release, setting up automated publishing to npm/PyPI/crates.io/Maven/Homebrew, deciding whether a change is major/minor/patch, writing release notes, adopting conventional commits or changesets, planning a 1.0,…