Skip to content

feat: automate crate and binary releases - #5

Open
lucarlig wants to merge 1 commit into
user/luca/import-mcp-manual-test-toolsfrom
user/luca/release-distribution
Open

feat: automate crate and binary releases#5
lucarlig wants to merge 1 commit into
user/luca/import-mcp-manual-test-toolsfrom
user/luca/release-distribution

Conversation

@lucarlig

@lucarlig lucarlig commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Summary

  • publish all five workspace crates to crates.io from pushes to main with release-plz
  • create an atomic GitHub release with attested, checksummed native binaries for Linux, macOS, and Windows
  • configure cargo-binstall to use only first-party release archives and never fall back to local compilation

Verification

  • cargo fmt --all --check
  • actionlint .github/workflows/release.yml
  • cargo clippy --workspace --all-targets --all-features -- -D warnings
  • cargo test --workspace --all-targets
  • cargo package --workspace --allow-dirty --no-verify
  • cargo build --release --locked --bin cf-integration
  • release archive contents and binary help smoke test

Required repository setup

Before merging, add the Actions secret CARGO_REGISTRY_TOKEN with permission to publish the five new crates. Also ensure Actions is allowed to create pull requests so release-plz can maintain release PRs.

Stacked on #4.

Signed-off-by: lucarlig <luca.carlig@ibm.com>
@lucarlig
lucarlig force-pushed the user/luca/release-distribution branch from 9b2a676 to 4b4c185 Compare August 27, 2026 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant