Bump Next.js and pin image optimiser - #33
Draft
ajhawkings wants to merge 1 commit into
Draft
Conversation
Deploying conradmargoles with
|
| Latest commit: |
5b9e899
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://901cdc1c.conradmargoles.pages.dev |
| Branch Preview URL: | https://agent-bump-next-and-pin-opti.conradmargoles.pages.dev |
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.
Summary
nextandeslint-config-nextfrom 16.2.6 to 16.2.12next-image-export-optimizerat 1.20.1Why
The Next.js patch picks up the current framework security fixes. The optimiser pin makes the reviewed version explicit;
npm ciwas already reproducible through the lockfile, but the manifest no longer permits a newer 1.x release to enter a future lockfile refresh.Validation
npm ci --ignore-scriptsnpm run lintnpm run build— 27 static pages exported and 2,520 image variants generatedRemaining audit output
npm audit --omit=devstill reports transitive high-severity advisories for PostCSS and Sharp. Next 16.2.12 still pins PostCSS 8.4.31, andnext-image-export-optimizer1.20.1 depends on Sharp^0.34.5; npm currently offers no compatible clean upgrade for either path. These dependencies are used during the trusted static build rather than in a long-running Pages server, which limits exposure but does not make the advisories disappear.