ci: bump actions to v5 and drop EOL Node versions#5
Merged
Conversation
GitHub is deprecating the Node 20 runtime that actions/checkout@v4 and actions/setup-node@v4 run on (forced to Node 24 on 2026-06-02). Bump both to v5, which runs on Node 24. Also align the tested Node versions with the package's engines field (>=22): the CI matrix drops 18 and 20 in favour of 22 and 24, and the release job moves from Node 20 to 22. Actions remain pinned to commit SHAs per the existing policy.
asachs01
added a commit
that referenced
this pull request
May 20, 2026
…#6) Salvages the still-relevant pieces of the abandoned fix/review-medium branch (its exports-map fix and smoke test already landed via #3/#5): - Regenerate package-lock.json via `npm audit fix`, clearing 16 of 19 dev-dependency advisories (incl. the critical/high vite findings). The remaining 3 live inside npm's own bundled deps under semantic-release and are not resolvable from here. - tsup `target` node18 -> node22, matching `engines.node` (>=22). - config.test.ts: replace `as any` with `as unknown as SuperOpsRegion`. No production dependencies were affected; the published package is unchanged at runtime.
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.
Why
The release workflow logs surfaced a deprecation warning:
Changes
actions/checkoutv4.3.1 → v5.0.1,actions/setup-nodev4.4.0 → v5.0.0 (both run on Node 24). Still pinned to commit SHAs per the existing policy.[18, 20, 22]→[22, 24]— aligns withengines.node(>=22). Node 18 and 20 were being tested despite being unsupported by the package.node-version20→22— matches the engines minimum.Verification
CI runs on this PR across Node 22 and 24; merge gated on green.