Repository navigation
Patch Next.js and keep PR security fast - #124
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
leemour
changed the title
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.
Update Next.js 16.3.5 to patched 16.3.6 and retain current browser-test/dependency settings. Production advisory audit reports zero critical findings after the update; fixed-content static image generation has no established attacker-controlled SVG path.
Keep PR security fast: add the pinned Gitleaks workflow and disable automatic Socket checks. Add an on-demand source/advisory/workflow security check. The protected deployment-workflow prerequisite remains in PR121 because the current CLI OAuth credential lacks workflow scope and the connected app lacks repository integration access; this PR changes no deployment workflow.
The dependency update passed local lint/types, 257 tests and a static build; the complete hosted browser/install suite passed in PR121. This PR verifies the focused change against current main, including concurrent browser-policy updates.