Skip to content

[Snyk] Upgrade next from 13.5.6 to 13.5.11#176

Closed
Loonz806 wants to merge 1 commit into
mainfrom
snyk-upgrade-1436ece9ce76ca514ff0f70b6fe81b39
Closed

[Snyk] Upgrade next from 13.5.6 to 13.5.11#176
Loonz806 wants to merge 1 commit into
mainfrom
snyk-upgrade-1436ece9ce76ca514ff0f70b6fe81b39

Conversation

@Loonz806
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade next from 13.5.6 to 13.5.11.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 31 versions ahead of your current version.

  • The recommended version was released 5 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Acceptance of Extraneous Untrusted Data With Trusted Data
SNYK-JS-NEXT-8025427
756 Proof of Concept
high severity Missing Authorization
SNYK-JS-NEXT-8520073
756 No Known Exploit
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-NEXT-8602067
756 No Known Exploit
critical severity Improper Authorization
SNYK-JS-NEXT-9508709
756 Mature
Release notes
Package name: next
  • 13.5.11 - 2025-03-27

    Note

    This release is backporting bug fixes. It does not include all pending features/changes on canary.

    Core Changes

    • Lock swc binaries version
  • 13.5.10 - 2025-03-24

    Note

    This release is backporting bug fixes. It does not include all pending features/changes on canary.

    Core Changes

    • Match subrequest handling for edge and node
  • 13.5.9 - 2025-03-22
  • 13.5.8 - 2024-12-21
  • 13.5.7 - 2024-09-17
  • 13.5.7-canary.37 - 2023-10-26
  • 13.5.7-canary.36 - 2023-10-26
  • 13.5.7-canary.35 - 2023-10-26
  • 13.5.7-canary.34 - 2023-10-26
  • 13.5.7-canary.33 - 2023-10-26
  • 13.5.7-canary.32 - 2023-10-26
  • 13.5.7-canary.31 - 2023-10-26
  • 13.5.7-canary.29 - 2023-10-26
  • 13.5.7-canary.28 - 2023-10-26
  • 13.5.7-canary.27 - 2023-10-25
  • 13.5.7-canary.26 - 2023-10-25
  • 13.5.7-canary.25 - 2023-10-24
  • 13.5.7-canary.24 - 2023-10-24
  • 13.5.7-canary.23 - 2023-10-24
  • 13.5.7-canary.22 - 2023-10-24
  • 13.5.7-canary.19 - 2023-10-23
  • 13.5.7-canary.18 - 2023-10-23
  • 13.5.7-canary.17 - 2023-10-23
  • 13.5.7-canary.16 - 2023-10-23
  • 13.5.7-canary.15 - 2023-10-22
  • 13.5.7-canary.14 - 2023-10-21
  • 13.5.7-canary.13 - 2023-10-20
  • 13.5.7-canary.12 - 2023-10-20
  • 13.5.7-canary.11 - 2023-10-19
  • 13.5.7-canary.10 - 2023-10-19
  • 13.5.7-canary.9 - 2023-10-19
  • 13.5.6 - 2023-10-18
from next GitHub release notes

Important

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

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

For more information:

Snyk has created this PR to upgrade next from 13.5.6 to 13.5.11.

See this package in npm:
next

See this project in Snyk:
https://app.snyk.io/org/loonz806/project/c30947da-4b6c-4e2f-a5e1-de9860f52f13?utm_source=github&utm_medium=referral&page=upgrade-pr
@vercel
Copy link
Copy Markdown

vercel Bot commented Aug 16, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
setup-example-next Ready Ready Preview Comment Aug 16, 2025 3:33am

@sonarqubecloud
Copy link
Copy Markdown

@stale
Copy link
Copy Markdown

stale Bot commented Oct 15, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale Bot added the wontfix This will not be worked on label Oct 15, 2025
@stale stale Bot closed this Oct 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wontfix This will not be worked on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants