ci: fix musl release builds by bumping taiki-e/install-action#263
Merged
Brooooooklyn merged 1 commit intovoidzero-dev:mainfrom May 6, 2026
Merged
Conversation
v2.27.8 lacks a native cargo-zigbuild manifest and falls back to cargo-binstall@1.6.3, whose old TOML parser rejects edition = "2024" in the current cargo-zigbuild manifest, breaking both musl release builds. v2.77.1 ships a native manifest that downloads the prebuilt binary directly, bypassing cargo-binstall entirely. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The last few releases seem to have been failing: https://github.com/voidzero-dev/oxc-angular-compiler/actions/runs/25418129497/job/74553825172
x86_64-unknown-linux-musl,aarch64-unknown-linux-musl) fail at theInstall cargo-zigbuildstep. Verified against run 25418129497.taiki-e/install-action@v2.27.8has no native manifest forcargo-zigbuildand falls back tocargo-binstall@1.6.3, whose old TOML parser rejectsedition = "2024"in the currentcargo-zigbuildCargo.toml.v2.77.1ships a nativecargo-zigbuildmanifest that downloads the prebuilt binary directly from therust-cross/cargo-zigbuildGitHub release, bypassingcargo-binstallentirely.While I have not been able to verify this, I believe this should resolve the issue.