Release

Cargo-dist generates .github/workflows/release.yml from dist-workspace.toml. Do not edit the generated workflow by hand. Change the distribution configuration and regenerate it through cargo-dist.

cargo-dist-version selects the configuration and generator contract. The cargo:cargo-dist entry in mise.toml installs the CLI, and mise.lock records its resolved release. Renovate updates the configuration version; weekly mise lock maintenance updates the CLI resolution.

Pull requests run the cargo-dist planning path. The plan covers five archive targets, shell and PowerShell installers, checksums, CycloneDX manifests, cargo-auditable metadata, GitHub attestations, and the package publication job.

Validate a release change

Run the plan and the complete local gate from the repository root:

just release-plan
just all

just all runs the lint lanes, native and frontend coverage, and the documentation build.

Build the Python artifacts from the checkout when changing Python packaging:

just package-sdist .tox/dist
just package-wheel

Inspect the cargo-dist plan for the expected targets, installers, checksums, attestations, and custom publish job.

Publish and verify

1. Run just release-plan and just all on the commit to tag.
2. Confirm that the version, lockfile, release notes, and generated plan refer to that commit.
3. Create the release tag expected by cargo-dist.
4. Wait for all build, host, and custom publication jobs to pass.
5. Download each archive and verify its checksum and GitHub attestation.
6. Inspect the CycloneDX manifest and cargo-auditable metadata from one executable per platform family.
7. Test the shell installer, PowerShell installer, and affected Python package on their target platforms.

A checksum detects changed bytes. The attestation ties those bytes to this repository, workflow, and source revision; verify both.

Owner-specific release instructions remain with the owner documentation.