Skip to content

RELEASING.md

Latest commit

 

History

History
54 lines (37 loc) · 1.76 KB

RELEASING.md

File metadata and controls

54 lines (37 loc) · 1.76 KB
Raw

Releasing Gold Digger

Gold Digger uses cargo-dist for automated cross-platform releases triggered by Git tags. For the full runbook with troubleshooting and recovery procedures, see docs/src/development/release-runbook.md.

Pre-Release Checklist

  • All quality gates pass: just ci-check
  • Version bumped in Cargo.toml
  • No stale version refs elsewhere: grep -rn "v0\.[0-9]" AGENTS.md CLAUDE.md README.md should return only the new version (todo #143)
  • Changelog regenerated: just changelog vX.Y.Z
  • dist-workspace.toml configuration is correct

Release Steps

  1. Create release branch

    git checkout main && git pull origin main
git checkout -b release/vX.Y.Z

  2. Update version and changelog

    # Edit Cargo.toml version field
just changelog vX.Y.Z
git add Cargo.toml CHANGELOG.md
git commit -m "chore: prepare vX.Y.Z release"

  3. Open PR and merge to main

    git push origin release/vX.Y.Z
# Open PR, get review, merge

  4. Tag and push

    git checkout main && git pull origin main
git tag vX.Y.Z
git push origin vX.Y.Z

  5. Monitor the release.yml workflow on GitHub Actions

Artifact Output

cargo-dist produces binaries for 7 target triples (macOS ARM64/Intel, Linux ARM64/x86_64-gnu, Linux x86_64-musl, Windows ARM64/x86_64) plus shell, PowerShell, MSI, and Homebrew installers. Each release also includes CycloneDX SBOMs and SHA256 checksums. The authoritative target list lives in dist-workspace.toml.

See Also