cargo-release 1.1.1 fixes packaging and pre-built binary CI upload inconsistencies

cargo-release version 1.1.1, released by the crate-ci/cargo-release repository on February 24, 2026, delivers targeted fixes for packaging and pre-built binary asset handling that had produced upload and CI inconsistencies. The new 1.1.1 tag specifically addresses the edge cases that were disrupting artifact uploads and the deterministic packaging steps used by Rust projects that publish pre-built binaries.

The repository release notes for crate-ci/cargo-release list the changes in 1.1.1 as fixes around packaging and pre-built binary assets; those fixes were framed as responses to inconsistent uploads and CI behavior. Maintainers pushed the package update in late February 2026 to make packaging steps and the generation of pre-built binaries behave predictably across CI runs that rely on cargo-release workflows.

If your project uses cargo-release to publish crates or pre-built binaries to CI artifact stores, upgrade to 1.1.1 and re-run your packaging and upload pipelines as soon as possible. Projects that saw intermittent failures during upload steps or mismatched packaging outputs in CI should test an upgrade path from their current cargo-release version to 1.1.1 and verify artifact integrity and CI exit codes after the upgrade.

The 1.1.1 release on Feb 24, 2026 is a maintenance patch aimed at stabilizing CI interactions rather than introducing new features. Pinning CI to crate-ci/cargo-release v1.1.1 or later will let teams reproduce packaging behavior consistently across branches and runners. Keep an eye on the crate-ci/cargo-release repository release notes for any follow-up commits if your pipeline still exhibits the earlier inconsistency patterns after updating to 1.1.1.