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 for new or improved capabilities.
• Use grafana-product: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 and svu.