Repository navigation
Conversation
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.
PR security stays limited to the fast secret scan; production deployment depends on the pinned shared security workflow. Critical production dependency/source findings and scanner failures stop deployment; noncritical findings remain for review. Automatic Socket checks are disabled. Existing ordinary tests and browser checks keep their triggers.
Update Next.js from 16.3.5 to the patched 16.3.6. Source review found fixed-content static image generation; no attacker-controlled SVG path was established. The production advisory audit now reports zero critical findings.
Validation: workflow YAML, prerequisite/permission checks and zizmor passed; lint, types, all 257 tests and the static production build passed locally. Hosted PR checks, including browser and Windows install checks, passed.