Release tfmcp
Treat publication as an irreversible operation. Keep the version synchronized
across Cargo.toml, Cargo.lock, server.json, the OCI identifier, and
Dockerfile.
Prepare
- Confirm the target version does not already exist on crates.io, as a Git
tag, or as a GitHub release.
- Update the synchronized version fields and add a dated
CHANGELOG.md
section.
- Update the tested Terraform version in CI and both Docker stages when the
release changes the supported baseline.
- Run
./Release.sh vX.Y.Z. Fix every failure; do not weaken gates to make a
release pass.
- Review
cargo package --list and the generated package contents for secrets,
temporary files, and stale release documents.
Publish
- Commit the verified release preparation on
main.
- Push
main and confirm the Rust CI workflow succeeds for that exact commit.
- Re-run
./Release.sh vX.Y.Z from the clean commit.
- Run
./Release.sh vX.Y.Z --publish.
- Verify the crates.io version, annotated Git tag, public GitHub release,
multi-platform GHCR image, and GitHub Actions results.
Never publish from a dirty worktree, bypass a failing check, reuse a release
version, or move an existing release tag.
Required gates
The release script is authoritative. It runs formatting, Clippy with warnings
denied, locked tests, audit, cargo coupling, similarity-rs, metadata
validation, diff checks, release build, package verification, and a crates.io
publish dry run.
Use cargo coupling --ai --git-months 6 --exclude-tests to diagnose structural
hotspots and similarity-rs src --skip-test --threshold 0.90 --min-lines 8 to
inspect duplicate candidates. Refactor findings only when the new boundary or
abstraction has a clear owner and preserves behavior.
1---2name: release3description: Prepare, verify, publish, or troubleshoot a tfmcp release to crates.io and GitHub. Use for version changes, release readiness checks, changelog preparation, tagging, or publication.4---56# Release tfmcp78Treat publication as an irreversible operation. Keep the version synchronized9across `Cargo.toml`, `Cargo.lock`, `server.json`, the OCI identifier, and10`Dockerfile`.1112## Prepare13141. Confirm the target version does not already exist on crates.io, as a Git15 tag, or as a GitHub release.162. Update the synchronized version fields and add a dated `CHANGELOG.md`17 section.183. Update the tested Terraform version in CI and both Docker stages when the19 release changes the supported baseline.204. Run `./Release.sh vX.Y.Z`. Fix every failure; do not weaken gates to make a21 release pass.225. Review `cargo package --list` and the generated package contents for secrets,23 temporary files, and stale release documents.2425## Publish26271. Commit the verified release preparation on `main`.282. Push `main` and confirm the Rust CI workflow succeeds for that exact commit.293. Re-run `./Release.sh vX.Y.Z` from the clean commit.304. Run `./Release.sh vX.Y.Z --publish`.315. Verify the crates.io version, annotated Git tag, public GitHub release,32 multi-platform GHCR image, and GitHub Actions results.3334Never publish from a dirty worktree, bypass a failing check, reuse a release35version, or move an existing release tag.3637## Required gates3839The release script is authoritative. It runs formatting, Clippy with warnings40denied, locked tests, audit, `cargo coupling`, `similarity-rs`, metadata41validation, diff checks, release build, package verification, and a crates.io42publish dry run.4344Use `cargo coupling --ai --git-months 6 --exclude-tests` to diagnose structural45hotspots and `similarity-rs src --skip-test --threshold 0.90 --min-lines 8` to46inspect duplicate candidates. Refactor findings only when the new boundary or47abstraction has a clear owner and preserves behavior.
nwiizo