ci: bump pinned actions in the dev release workflow#2
Merged
Conversation
CMGS
force-pushed
the
ci/bump-actions
branch
2 times, most recently
from
July 23, 2026 04:46
3d74915 to
cd8936c
Compare
The pinned action versions had drifted; each now points at the major that is current today. Publishing moves to a job that waits on both builds, since two matrix jobs writing one rolling release race each other, and the artifact round-trip drops the executable bit the release job needs. Signed-off-by: CMGS <ilskdw@gmail.com>
Cargo.toml's rust-version is a floor, not the version to build with; upstream CI builds with stable. build-info.json already records the exact rustc, so following stable keeps provenance intact. Signed-off-by: CMGS <ilskdw@gmail.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
1 participant
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.
Part of an org-wide CI/CD refresh. Bumps only the actions in our own
dev-release.yaml; the upstream workflow files on this branch are deliberately left untouched so the fork keeps rebasing onto upstream cleanly.Each target is the current
latestrelease major, read fromgh api repos/<action>/releases/latest.The Rust pin is deliberately NOT bumped: upstream Cargo.toml sets
package.rust-version = "1.89.0", so our workflow pin already matches the project MSRV rather than lagging it.Gates
CI is the gate: a push to
devruns this workflow end to end and publishes the rolling dev release.