Use this checklist for every release to keep engineering, documentation, and announcements in sync.
- Confirm target branch and clean working tree.
- Confirm version alignment across
plugin.yaml,gemini-extension.json,mcp-server/package.json, andmanifest.json. - Confirm
CHANGELOG.mdhas a section for the target version. - Create or update
RELEASE-{version}.md.
Ensure RELEASE-{version}.md includes these required sections:
-
## Overview -
## Highlights -
## Full Changelog
Recommended additions:
- Upgrade notes or migration guidance
- CI and reliability impact summary
- Links to key workflow or config changes
- Push release commit(s) to the release branch.
- Create GitHub release tag
v{version}. - Publish release using
RELEASE-{version}.mdas notes. - Verify release page renders required sections correctly.
- Post a short release summary in GitHub Discussions (or project announcement channel).
- Share a concise internal update (Slack/Teams/email) with:
- version
- top 3 to 5 changes
- links to release notes and changelog
- Update any marketplace-facing or onboarding docs with new version references.
- Confirm
release-consistency-guard.ymlpasses on the release commit. - Confirm
ci-integrity-guards.ymlpasses on the release commit. - Confirm docs lint and CI checks pass on main.
- Confirm no stale version pins remain in public examples.
- Review latest
branch-hygiene-report.ymlsummary for stale long-lived release branches.
Use this announcement template:
Accessibility Agents v{version} is now live.
Highlights:
- {change 1}
- {change 2}
- {change 3}
Release notes: {release-url}
Changelog: {changelog-url}