Skip to content

AGENTS.md

Latest commit

 

History

History
25 lines (20 loc) · 1.15 KB

AGENTS.md

File metadata and controls

25 lines (20 loc) · 1.15 KB
Raw

AGENTS

Release Tag Guardrails

Follow this checklist every time you cut a release tag.

  1. Pick the release version, for example 0.2.0-beta.9.0.9. If the user asks for a minor update on an active release line, keep the chosen minor version (for example 0.3.0) and do not bump again to a patch or another new version unless the user explicitly requests a different version.
  2. Update all release metadata files to the same version:
    • Cargo.toml ([package].version)
    • npm/package.json (version)
    • go/internal/installer/installer.go (const version = "...")
  3. Validate versions before tagging:
    • python scripts/verify-release-versions.py v<version>
  4. Commit the version and workflow changes to main.
  5. Create an annotated tag using the v prefix:
    • git tag -a v<version> -m "Release v<version>"
  6. Push branch first, then push the tag:
    • git push origin main
    • git push origin v<version>

Why this is required

  • .github/workflows/release.yml triggers on tags matching v*.
  • The release workflow runs scripts/verify-release-versions.py.
  • If Go/Cargo/npm versions are not synced before tagging, release fails.