Repository navigation
ci: follow current stable runtimes and tools - #6516
Merged
Merged
Conversation
Use rolling runtime and runner channels, supported official action aliases and daily grouped updates. Bootstrap current Cargo tools through live cargo-binstall resolution while retaining reviewed external action SHA pins. Generated-by: OpenAI Codex
1 of 3 tasks
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
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
Follow current stable CI tooling instead of freezing runtime and utility patch releases in workflow files. Node, npm, Zig and hosted runners use their rolling latest channels; Rust keeps stable and Python uses the latest stable 3.x. Select the distribution's libclang through llvm-config while preserving the release target and glibc baseline.
Official GitHub actions use supported major aliases. External actions retain ASF-required reviewed SHA pins: update taiki-e/install-action to reviewed v2.88.1 and retain the approved setup-zig v2.2.1 revision. The pinned installer bootstraps cargo-binstall, which then updates itself and installs current Cargo tools from the live registry, rather than relying on the installer's frozen tool manifest. Daily grouped Dependabot updates cover both default and rust-preview branches, including new action majors.
Keep the existing verified releases/latest mbx installation. Cargo target cache keys are independent of mbx version, so updating mbx does not discard compatible compiler output.
Verification
AI use
OpenAI Codex researched the current releases and policies, reviewed the installer update, and implemented these changes.
Generated-by: OpenAI Codex