ci: bump actions/upload-artifact to v7 for the Node 24 runtime - #2
Merged
Conversation
GitHub deprecated the Node 20 action runtime; every job in the release workflow warned that upload-artifact v4 targets Node 20 and is being forced onto Node 24. v7.0.1 runs on Node 24 natively (v5 was the runtime bump; v6/v7 only added opt-in features such as unzipped direct uploads), and the inputs used here (name/path/if-no-files-found) are unchanged. All other pinned actions (checkout v6.1.0, setup-node v6.5.0, cache v6.1.0, pnpm/action-setup v6.0.9) already target Node 24 and produced no deprecation annotations in run 30985104980.
This was referenced Aug 18, 2026
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.
Summary
Release-workflow run 30985104980 emitted a deprecation warning on every job:
This bumps the pin to
actions/upload-artifact@v7.0.1(043fb46d), which targets Node 24 natively.archive: falsedirect-upload mode. None of these change the inputs used here (name/path/if-no-files-found).checkoutv6.1.0,setup-nodev6.5.0,cachev6.1.0,pnpm/action-setupv6.0.9) already target Node 24 — run 30985104980 produced no annotations for them, soupload-artifactis the only pin that needed a bump.Verification
release.ymlonly runs onworkflow_dispatch, so this cannot be exercised pre-merge; adry_run=truedispatch after merge confirms the warning is gone.