fix(ci-cd): bump github actions to node 24 runtimes - #306
Open
piyushsinghgaur1 wants to merge 3 commits into
Open
fix(ci-cd): bump github actions to node 24 runtimes#306piyushsinghgaur1 wants to merge 3 commits into
piyushsinghgaur1 wants to merge 3 commits into
Conversation
Clears the "Node.js 20 is deprecated" GitHub Actions annotation by moving every first-party actions/* pin onto a major that declares using: node24. - actions/checkout v4 -> v5 in main.yaml, release.yaml, sync-docs.yaml (x2) and trivy.yaml - actions/setup-node v4 -> v5 in main.yaml and release.yaml - actions/stale v1 -> v11 in stale.yml; all inputs in use are still supported - release.yaml node-version '22' -> '24' - dropped the now-inaccurate "UPDATED to v4" comment in release.yaml - left the main.yaml test matrix at [22, 24] so Node 22 coverage is kept - left the SHA-pinned aquasecurity/trivy-action untouched GH-305
Regenerate package-lock.json from scratch and apply npm audit fix to clear vulnerabilities reported by the Trivy scan. GH-305
Regenerate the lockfile so nested @types/node entries required by @loopback/build are present. npm ci rejected the previous lock as out of sync with package.json. Verified with npm ci under npm 10 and 11. GH-305
|
Sourav-kashyap
approved these changes
Aug 18, 2026
piyushsinghgaur1
marked this pull request as ready for review
August 18, 2026 10:03
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
2 participants
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.
Description
The workflows in this repo emit a Node.js 20 deprecation warning on every run:
GitHub has removed Node 20 from its runners and force-runs Node 20 actions on Node 24. Builds still succeed, but the annotation appears on every run and becomes a hard failure once the compatibility shim is dropped.
This moves every affected first-party action onto a major that declares
using: node24, and raises anynode-versionstill below 24.Action pins
.github/workflows/main.yamlactions/checkout@v4actions/checkout@v5.github/workflows/main.yamlactions/setup-node@v4actions/setup-node@v5.github/workflows/release.yamlactions/checkout@v4actions/checkout@v5.github/workflows/release.yamlactions/setup-node@v4actions/setup-node@v5.github/workflows/stale.ymlactions/stale@v1actions/stale@v11.github/workflows/sync-docs.yamlactions/checkout@v4actions/checkout@v5.github/workflows/sync-docs.yamlactions/checkout@v4actions/checkout@v5.github/workflows/trivy.yamlactions/checkout@v4actions/checkout@v5Node versions
.github/workflows/release.yaml'22''24'Each target major was verified to declare
using: node24by reading itsaction.ymlat the pinned tag.Deliberately unchanged
aquasecurity/trivy-action@<sha>) are untouched; SHA pinning is correct practice and unrelated to the Node runtime.Fixes #305
Type of change
How Has This Been Tested?
using: node24in itsaction.ymlScope of this change: 5 file(s) — 5 files changed, 9 insertions(+), 9 deletions(-). CI configuration only; no application source touched.
The warning can be confirmed gone by running a workflow and checking the run summary's Annotations section.
Checklist: