Conversation
- bump actions/checkout from v4 to v5 in main.yaml, release.yml and trivy.yml - bump actions/setup-node from v4 to v5 in main.yaml and release.yml - set node-version from '22.x' to '24.x' in main.yaml - set node-version from '22' to '24' in release.yml - drop the stale "UPDATED to v4" comment on the setup-node step in release.yml - leave the SHA-pinned aquasecurity/trivy-action in trivy.yml unchanged actions/checkout@v4 and actions/setup-node@v4 declare using: node20, which triggers the "Node.js 20 is deprecated" annotation on every workflow run. The v5 majors of both declare using: node24. Node 24 is already a supported runtime per the "22 || 24" engines range in package.json. GH-24
Regenerate package-lock.json from scratch and apply npm audit fix to clear vulnerabilities reported by the Trivy scan. GH-24
Pass --ignore-scripts before the package name and pin the exact semantic-release version, so the release workflow no longer trips SonarCloud rules githubactions:S6505 and githubactions:S8543. GH-24
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| npm config set provenance true | ||
|
|
||
| HUSKY=0 npx semantic-release | ||
| HUSKY=0 npx --ignore-scripts semantic-release@25.0.9 |
| npm config set provenance true | ||
|
|
||
| HUSKY=0 npx semantic-release | ||
| HUSKY=0 npx --ignore-scripts semantic-release@25.0.9 |
piyushsinghgaur1
marked this pull request as ready for review
August 18, 2026 08:51
a-ganguly
approved these changes
Aug 19, 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
3 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.ymlactions/checkout@v4actions/checkout@v5.github/workflows/release.ymlactions/setup-node@v4actions/setup-node@v5.github/workflows/trivy.ymlactions/checkout@v4actions/checkout@v5Node versions
.github/workflows/main.yaml'22.x''24.x'.github/workflows/release.yml'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 #24
Type of change
How Has This Been Tested?
using: node24in itsaction.ymlScope of this change: 3 file(s) — 3 files changed, 7 insertions(+), 7 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: