Repository navigation
chore: pin patched Node.js security releases - #4
Open
factory-nizar wants to merge 1 commit into
Open
factory-nizar wants to merge 1 commit into
factory-nizar wants to merge 1 commit into
Conversation
Apply the November Node.js security fixes without migrating runtime majors. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
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
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
Developers and automation in this repository need the November Node.js security fixes. This PR selects Node 24.22.3 for the existing supported runtime majors. It makes the patched baseline explicit without a major-version migration.
Source: security announcement.
Changes
.github/workflows/release.ymlValidation
git diff --check 04fa2e7d4143 a19a29e3d4ed: passed.Full application lint/typecheck/test/build/E2E and cloud/deployment gates were not run, under the user's explicit scoped-local-checks-plus-PR-CI approval. Existing deployments and machines were not changed. Required CI and human review remain merge gates.
Risk and scope
Supported majors, application code, dependency manifests, lockfiles, and compatibility ranges remain unchanged. EOL runtime selections, where present, are deliberately not migrated. No merge or deployment is part of this PR.