Repository navigation
Patch Next.js security advisories blocking deployment - #144
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.
The production dependency audit now blocks releases on Next.js advisories GHSA-2464-fhr4-w9xw and GHSA-p3m5-59mp-jv5r. Update Commerce and the sales showcase from 16.3.8 to the patched 16.4.1 release, refresh the lockfile, and extend the existing security-floor regression check to prevent a downgrade. Preserve the existing Next.js contributor guidance outside framework-managed markers: Next.js 16.4 removes managed blocks when the already-disabled
agentRulesoption is false, otherwise dirtying the checkout during UI qualification. Application configuration stays the same.Validation: both production builds, dependency-floor tests, production dependency audit, local browser smoke, and confirmation that the framework leaves both apps’ contributor guidance unchanged; full CI and deployment checks run on the PR.