Repository navigation
chore(ci): update GitHub Actions to latest majors - #11792
Merged
Merged
Conversation
Most of the drift is the Node 20 -> Node 24 runtime migration that landed across actions/* and docker/* in late 2025 / 2026. Root cause of the rot: .github/dependabot.yml had no github-actions ecosystem entry, so nothing was proposing these bumps — added one, grouped weekly. | Action | From | To | | --- | --- | --- | | actions/checkout | v4, v6 | v7 | | actions/setup-node | v4 | v7 | | actions/setup-python | v5 | v7 | | actions/cache, actions/cache/restore | v4 | v6 | | actions/upload-artifact | v4 | v7 | | actions/download-artifact | v4 | v8 | | actions/github-script | v7 | v9 | | actions/labeler | v6 | v7 | | docker/login-action | v3 | v4 | | docker/setup-buildx-action | v3 | v4 | | docker/setup-qemu-action | v3 | v4 | | docker/build-push-action | v6 | v7 | | docker/bake-action | v5 | v7 | | codecov/codecov-action | v5 | v7 | | nick-fields/retry | v3 | v4 | | peter-evans/dockerhub-description | v2 | v5 | | aws-actions/configure-aws-credentials | v4 | v6 | | svenstaro/upx-action | v2 | v3 | Renamed inputs the new majors require: - docker/bake-action v7 merged `workdir` into `source`. v6 also flipped `source` to default to the git context, so passing the local path explicitly is what preserves the current path-context behavior. - svenstaro/upx-action 3.0.0 dropped `file` for `files`. Replaced two actions that have no newer release: - allenevans/set-env (6 call sites) -> plain `>> "$GITHUB_ENV"`. The Windows OpenSSL blocks use `shell: bash` explicitly, since the default there is PowerShell, which writes UTF-16 and corrupts $GITHUB_ENV. - hramos/label-actions@v1 -> dessant/label-actions@v5. Both v1 and v2 of the hramos fork declare `runs.using: node12`; dessant is the maintained upstream it was forked from. Renamed `repo-token` to `github-token`, added explicit permissions, and dropped the checkout step — v5 fetches .github/label-actions.yml over the API. Verification: actionlint 1.7.12 is clean, and clean on an origin/master baseline too. Separately, all 215 remote `uses:` steps had their `with:` keys validated against each action's action.yml at the new ref — actionlint alone does not catch renamed inputs, since it passed on master with the stale `workdir`/`file` keys still in place. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
waralexrom
approved these changes
Sep 7, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #11792 +/- ##
==========================================
- Coverage 84.67% 80.21% -4.47%
==========================================
Files 261 500 +239
Lines 86451 105649 +19198
Branches 0 3885 +3885
==========================================
+ Hits 73204 84748 +11544
- Misses 13247 20352 +7105
- Partials 0 549 +549
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
ovr
force-pushed
the
update-github-actions
branch
from
September 7, 2026 19:21
1589c61 to
7a7534a
Compare
1 of 4 tasks
ovr
added a commit
that referenced
this pull request
Sep 9, 2026
…ode@v7 npmrc (#11816) `setup-node` with `registry-url` writes an .npmrc containing `//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}` and points `NPM_CONFIG_USERCONFIG` at it. Up to v6 it also exported a placeholder value for that variable; v7 only exports it when the user supplied one: | setup-node | NODE_AUTH_TOKEN exported | | ---------- | ---------------------------------------------------------- | | v4/v5/v6 | `process.env.NODE_AUTH_TOKEN \|\| 'XXXXX-XXXXX-XXXXX-XXXXX'` | | v7 | only if present in `process.env` | We publish via OIDC trusted publishing and set no token, so since #11792 bumped the action to v7 every yarn 1 command in the `npm` job dies with `Failed to replace env in config: ${NODE_AUTH_TOKEN}` (npm tolerates the unresolved value, yarn does not). That killed the v1.7.36 release at `yarn policies set-version`, and silently emptied the yarn cache key before that, since `yarn cache dir` failed inside a command substitution. The auth line is unused with OIDC, so drop it and keep the `registry=` one. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
ovr
added a commit
that referenced
this pull request
Sep 9, 2026
…ode@v7 npmrc (#11816) `setup-node` with `registry-url` writes an .npmrc containing `//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}` and points `NPM_CONFIG_USERCONFIG` at it. Up to v6 it also exported a placeholder value for that variable; v7 only exports it when the user supplied one: | setup-node | NODE_AUTH_TOKEN exported | | ---------- | ---------------------------------------------------------- | | v4/v5/v6 | `process.env.NODE_AUTH_TOKEN \|\| 'XXXXX-XXXXX-XXXXX-XXXXX'` | | v7 | only if present in `process.env` | We publish via OIDC trusted publishing and set no token, so since #11792 bumped the action to v7 every yarn 1 command in the `npm` job dies with `Failed to replace env in config: ${NODE_AUTH_TOKEN}` (npm tolerates the unresolved value, yarn does not). That killed the v1.7.36 release at `yarn policies set-version`, and silently emptied the yarn cache key before that, since `yarn cache dir` failed inside a command substitution. The auth line is unused with OIDC, so drop it and keep the `registry=` one. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This branch was successfully deployed
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.
Check List
Description of Changes Made
Brings 18 actions up to their latest majors — mostly the Node 20 → Node 24 runtime migration that landed across
actions/*anddocker/*:checkout→v7,setup-node/setup-python→v7,cache→v6,upload-artifact→v7,download-artifact→v8,github-script→v9,labeler→v7, all fourdocker/*→v4/v7,codecov→v7,nick-fields/retry→v4,dockerhub-description→v5,configure-aws-credentials→v6,upx-action→v3. Two of those majors renamed inputs, sodocker/bake-action'sworkdir:becomessource:andupx-action'sfile:becomesfiles:. Also replaced two actions that have no newer release:allenevans/set-env(6 call sites) with plain>> "$GITHUB_ENV", and the node12hramos/label-actions@v1with its maintained upstreamdessant/label-actions@v5. Added a grouped weeklygithub-actionsentry to.github/dependabot.yml— its absence is why everything had drifted 1–4 majors behind. All runners are GitHub-hosted and everycontainer:image in use is glibc ≥ 2.31, above Node 24's 2.28 floor, so the runtime bump is safe throughout.Verification
actionlint1.7.12 passes clean, and passes on anorigin/masterbaseline too. Separately, all 215 remoteuses:steps had theirwith:keys validated against each action'saction.ymlat the new ref — worth noting because actionlint alone does not catch renamed inputs: it passed on master with the staleworkdir:/file:keys still in place. Thebake-actionrename is exercised by this PR (the diff touchescross-images.yml);master.yml,publish.yml,post-release.yml,rust-cubestore-master.ymland theupxsteps only fire on master/tags/schedule, so they need a look at merge time.