[Snyk] Security upgrade next from 12.2.4 to 13.5.4

[t10-13rocket]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	551/1000 Why? Recently disclosed, Has a fix available, CVSS 5.3	Improper Input Validation SNYK-JS-POSTCSS-5926692	Yes	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: next

The new version differs by 250 commits.

• 1e8dca4 v13.5.4
• 9e24d6f v13.5.4-canary.11
• 281ae41 Fix build output logging order (#56335)
• d7626ff Revert "misc: shortcut styled-jsx in external resolution (#56291)" (#56334)
• db48052 v13.5.4-canary.10
• 7df92b8 test: add flaky turbopack integration tests to manifest (#56309)
• eeb9b33 fix: Invalid URL (404) provided on server actions error (#56323)
• 3172cfe fix: support both decoded and encoded url requests of conventioned files (#56187)
• a2f9ef5 fix(next/client): keep hash when navigating from app to pages router (#56223)
• a970f28 Add code freeze GitHub actions for releasing (#56325)
• 5fbc23e misc: fix instrumentation with bundled server (#56318)
• 98432a4 Remove buildId test as it's no longer relevant (#56316)
• 86274e6 fix(#53190): add missing crossOrigin to assetsPrefix resources (#56311)
• e970e05 Reland static prefetches & fix prefetch bailout behavior (#56228)
• be952fb fix: typo in `with-stripe-typescript` example (#56274)
• 7f60cc8 Support serverRuntimeConfig and publicRuntimeConfig in Turbopack (#56310)
• 8d18ad6 update webp crate (#56307)
• ac95a20 Fix flaky test for size output (#56303)
• dba978f misc: shortcut styled-jsx in external resolution (#56291)
• 458dab8 misc: update code owners (#56290)
• 5254aae Update image.mdx (#56266)
• 0d4859b Update image.mdx (#56269)
• 59bda2d More Turbopack fixes (#56299)
• ecd94c1 misc: enable source maps for bundled runtime (#56289)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Improper Input Validation

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.