Skip to content

Bugfix: Pin cargo-xbuild to v0.6.5 in CI#260

Open
Inquisitor-201 wants to merge 2 commits intosyswonder:devfrom
Inquisitor-201:clk-dev-dbg-cargo-xbuild
Open

Bugfix: Pin cargo-xbuild to v0.6.5 in CI#260
Inquisitor-201 wants to merge 2 commits intosyswonder:devfrom
Inquisitor-201:clk-dev-dbg-cargo-xbuild

Conversation

@Inquisitor-201
Copy link
Contributor

The CI pipeline recently started failing because cargo-xbuild v0.6.6 (and its dependencies) requires edition2024, which is not supported by our current nightly Rust toolchain (1.80.0).

This PR locks the version to v0.6.5 to restore CI stability while keeping the existing toolchain environment.

Related Error:
feature edition2024 is required but not stabilized in this version of Cargo

@github-actions github-actions bot added the bug Something isn't working label Feb 25, 2026
@li041
Copy link
Contributor

li041 commented Feb 25, 2026

Maybe cargo install cargo-xbuild is redundant. The built-in -Zbuild-std feature in Cargo's nightly channel now handles cross-compiling the sysroot (core, alloc, std) automatically, and I do not see any usage of cargo-xbuild in our repo.

@Inquisitor-201
Copy link
Contributor Author

Maybe cargo install cargo-xbuild is redundant. The built-in -Zbuild-std feature in Cargo's nightly channel now handles cross-compiling the sysroot (core, alloc, std) automatically, and I do not see any usage of cargo-xbuild in our repo.

Thanks, I'll see if it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants