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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Node version inconsistency across CI workflows after upgrade
Medium Severity
Updating
.nvmrcto24creates a version mismatch across CI environments. Thecode-check.ymlworkflow reads from.nvmrc(now Node 24), butaudit.ymlandextract-strings.ymlstill hardcodenode-version: "20.x". Previously all environments consistently used Node 20; now some CI jobs run on 24 while others remain on 20, which can lead to differingnpm auditresults and inconsistent behavior.