Skip to content
This repository was archived by the owner on Dec 31, 2025. It is now read-only.

[Snyk] Upgrade next from 15.3.2 to 15.3.4#3

Open
Clupai8o0 wants to merge 1 commit intomainfrom
snyk-upgrade-5534b506fcbe1736254bb7a4cf1ea521
Open

[Snyk] Upgrade next from 15.3.2 to 15.3.4#3
Clupai8o0 wants to merge 1 commit intomainfrom
snyk-upgrade-5534b506fcbe1736254bb7a4cf1ea521

Conversation

@Clupai8o0
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade next from 15.3.2 to 15.3.4.

ℹ️ 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 2 versions ahead of your current version.

  • The recommended version was released 25 days ago.

Release notes
Package name: next
  • 15.3.4 - 2025-06-18

    Note

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

    Core Changes

    • [metadata] render streaming metadata on the top level (#80566)
    • [fix] clone the config module to avoid mutation (#80573)

    Credits

    Huge thanks to @ huozhi for helping!

  • 15.3.3 - 2025-05-29
  • 15.3.2 - 2025-05-06
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.

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 15.3.2 to 15.3.4.

See this package in npm:
next

See this project in Snyk:
https://app.snyk.io/org/clupai8o0/project/ed54e412-ebbe-438e-9505-1b4025752cb8?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants