Skip to content

[Snyk] Security upgrade next from 15.5.12 to 15.5.15 - #351

Closed
peterj wants to merge 1 commit into
mainfrom
snyk-fix-e750b46d654dc0f252fed83cdc8506b7
Closed

[Snyk] Security upgrade next from 15.5.12 to 15.5.15#351
peterj wants to merge 1 commit into
mainfrom
snyk-fix-e750b46d654dc0f252fed83cdc8506b7

Conversation

@peterj

@peterj peterj commented Apr 15, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-NEXT-15954202
  721  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@kristin-kronstain-brown

Copy link
Copy Markdown
Contributor

Closing: this is now addressed on the kkb-hugo-docs-migration branch (#406, commit 7adc835), which stays on the Next 15 line:

  • next^15.5.21 (resolves 15.5.22)
  • new overrides: postcss^8.5.23, sharp^0.35.0

All 24 Next.js advisories that applied to 15.5.12 are fixed as of 15.5.21, so the 15.x line is sufficient — npm audit now reports next, postcss, and sharp clean. Verified with npm ci and a full make build (Hugo docs + OpenNext worker); CI is green on #406.

Superseded: #406 lands 15.5.22, which is higher than this PR's target on the same release line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants