Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade next from 14.2.2 to 14.2.13 #3

Open
wants to merge 1 commit into
base: canary
Choose a base branch
from

Conversation

eronisking
Copy link
Owner

@eronisking eronisking commented Oct 12, 2024

snyk-top-banner

Snyk has created this PR to upgrade next from 14.2.2 to 14.2.13.

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

  • The recommended version was released on 22 days 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
649 No Known Exploit
Release notes
Package name: next
  • 14.2.13 - 2024-09-20

    Note

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

    Core Changes

    • Fix missing cache-control on SSR app route (#70265)
    • feat: add polyfill of URL.canParse for browser compatibility (#70228)
    • Fix vercel og package memory leak (#70214)
    • Fix startTime error on Android 9 with Chrome 74 (#67391)

    Credits

    Huge thanks to @ raeyoung-kim, @ huozhi, @ devjiwonchoi, and @ ijjk for helping!

  • 14.2.12 - 2024-09-17

    Note

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

    Core Changes

    • update prefetching jsdoc & documentation (#68047)
    • Ensure we chunk revalidate tag requests (#70189)
    • (backport) fix(eslint): allow typescript-eslint v8 (#70090)
    • [ppr] Don't mark RSC requests as /_next/data requests (backport of #66249) (#70083)

    Credits

    Huge thanks to @ alvarlagerlof, @ wyattjoh, @ delbaoliveira, and @ ijjk for helping!

  • 14.2.11 - 2024-09-12
  • 14.2.10 - 2024-09-11
  • 14.2.9 - 2024-09-09
  • 14.2.8 - 2024-09-04
  • 14.2.7 - 2024-08-27
  • 14.2.6 - 2024-08-21
  • 14.2.5 - 2024-07-10
  • 14.2.4 - 2024-06-11
  • 14.2.3 - 2024-04-24
  • 14.2.2 - 2024-04-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:

Description by Korbit AI

What change is being made?

Upgrade the "next" package from version 14.2.2 to 14.2.13 in the examples/with-storybook/package.json file.

Why are these changes being made?

This upgrade addresses potential security vulnerabilities and bug fixes in the "next" package, ensuring the project remains up-to-date with the latest stable release. Keeping dependencies current is crucial for maintaining software security and performance.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Copy link

korbit-ai bot commented Oct 12, 2024

👋 I'm here to help you review your pull request. When you're ready for me to perform a review, you can comment anywhere on this pull request with this command: /korbit-review.

As a reminder, here are some helpful tips on how we can collaborate together:

  • To have me re-scan your pull request, simply re-invoke the /korbit-review command in a new comment.
  • You can interact with me by tagging @korbit-ai in any conversation in your pull requests.
  • On any comment I make on your code, please leave a 👍 if it is helpful and a 👎 if it is unhelpful. This will help me learn and improve as we work together
  • Lastly, to learn more, check out our Docs.

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.

2 participants