Skip to content

fix(ci): install cargo-release with +stable toolchain#430

Merged
kariy merged 1 commit into
mainfrom
fix/ci-cargo-install-stable
May 20, 2026
Merged

fix(ci): install cargo-release with +stable toolchain#430
kariy merged 1 commit into
mainfrom
fix/ci-cargo-install-stable

Conversation

@kariy
Copy link
Copy Markdown
Member

@kariy kariy commented May 20, 2026

Summary

The release-dispatch workflow's cargo install cargo-release --locked step fails because the repo's rust-toolchain.toml pins 1.90.0, which overrides the workflow's stable toolchain setup. The latest cargo-release (1.1.2) requires rustc 1.91+, so the build aborts:

error: cannot install package `cargo-release 1.1.2`, it requires rustc 1.91 or newer, while the currently active rustc version is 1.90.0

(Failed run: https://github.com/dojoengine/torii/actions/runs/26179260967)

Fix

Use cargo +stable install for both helper CLIs (cargo-release, cargo-get). These tools don't compile this repo — they just consume/edit Cargo.toml — so there's no reason to honor the repo's pinned toolchain when building them. +stable sidesteps the override without touching rust-toolchain.toml. Applied to cargo-get proactively so the next MSRV bump doesn't break it the same way.

The repo's rust-toolchain.toml pins 1.90.0, which overrides the
workflow's stable setup during cargo install. cargo-release 1.1.2
requires rustc 1.91, so the install fails. Use +stable to compile
the helper CLIs against the latest toolchain regardless of the repo
override. Same fix applied to cargo-get to prevent future drift.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@kariy kariy merged commit 483f37a into main May 20, 2026
1 check failed
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