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.1.4 to 14.2.10 #340

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

Conversation

lryanle
Copy link
Owner

@lryanle lryanle commented Oct 3, 2024

snyk-top-banner

Snyk has created this PR to upgrade next from 14.1.4 to 14.2.10.

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

  • The recommended version was released on 21 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
165 No Known Exploit
Release notes
Package name: next
  • 14.2.10 - 2024-09-11

    Note

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

    Core Changes

    • Remove invalid fallback revalidate value (#69990)
    • Revert server action optimization (#69925)
    • Add ability to customize Cache-Control (#69802)

    Credits

    Huge thanks to @ huozhi and @ ijjk for helping!

  • 14.2.9 - 2024-09-09

    Note

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

    Core Changes

    • Revert "Fix esm property def in flight loader (#66990)" (#69749)
    • Disable experimental.optimizeServer by default to fix failed server action (#69788)
    • Fix middleware fallback: false case (#69799)
    • Fix status code for /_not-found route (#64058) (#69808)
    • Fix metadata prop merging (#69807)
    • create-next-app: fix font file corruption when using import alias (#69806)

    Credits

    Huge thanks to @ huozhi, @ ztanner, @ ijjk, and @ lubieowoce for helping!

  • 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
  • 14.2.1 - 2024-04-12
  • 14.2.1-canary.7 - 2024-04-15
  • 14.2.1-canary.6 - 2024-04-15
  • 14.2.1-canary.5 - 2024-04-14
  • 14.2.1-canary.4 - 2024-04-13
  • 14.2.1-canary.3 - 2024-04-12
  • 14.2.1-canary.2 - 2024-04-12
  • 14.2.1-canary.1 - 2024-04-12
  • 14.2.1-canary.0 - 2024-04-11
  • 14.2.0 - 2024-04-11
  • 14.2.0-canary.67 - 2024-04-11
  • 14.2.0-canary.66 - 2024-04-11
  • 14.2.0-canary.65 - 2024-04-10
  • 14.2.0-canary.64 - 2024-04-09
  • 14.2.0-canary.63 - 2024-04-08
  • 14.2.0-canary.62 - 2024-04-07
  • 14.2.0-canary.61 - 2024-04-06
  • 14.2.0-canary.60 - 2024-04-05
  • 14.2.0-canary.59 - 2024-04-05
  • 14.2.0-canary.58 - 2024-04-05
  • 14.2.0-canary.57 - 2024-04-04
  • 14.2.0-canary.56 - 2024-04-04
  • 14.2.0-canary.55 - 2024-04-03
  • 14.2.0-canary.54 - 2024-04-02
  • 14.2.0-canary.53 - 2024-04-02
  • 14.2.0-canary.52 - 2024-04-01
  • 14.2.0-canary.51 - 2024-04-01
  • 14.2.0-canary.50 - 2024-03-30
  • 14.2.0-canary.49 - 2024-03-29
  • 14.2.0-canary.48 - 2024-03-28
  • 14.2.0-canary.47 - 2024-03-28
  • 14.2.0-canary.46 - 2024-03-27
  • 14.2.0-canary.45 - 2024-03-27
  • 14.2.0-canary.44 - 2024-03-26
  • 14.2.0-canary.43 - 2024-03-25
  • 14.2.0-canary.42 - 2024-03-25
  • 14.2.0-canary.41 - 2024-03-24
  • 14.2.0-canary.40 - 2024-03-23
  • 14.2.0-canary.39 - 2024-03-22
  • 14.2.0-canary.38 - 2024-03-22
  • 14.2.0-canary.37 - 2024-03-22
  • 14.2.0-canary.36 - 2024-03-21
  • 14.2.0-canary.35 - 2024-03-21
  • 14.2.0-canary.34 - 2024-03-20
  • 14.2.0-canary.33 - 2024-03-19
  • 14.2.0-canary.32 - 2024-03-19
  • 14.2.0-canary.31 - 2024-03-19
  • 14.2.0-canary.30 - 2024-03-18
  • 14.2.0-canary.29 - 2024-03-18
  • 14.2.0-canary.28 - 2024-03-18
  • 14.2.0-canary.27 - 2024-03-17
  • 14.2.0-canary.26 - 2024-03-16
  • 14.2.0-canary.25 - 2024-03-16
  • 14.2.0-canary.24 - 2024-03-15
  • 14.2.0-canary.23 - 2024-03-14
  • 14.2.0-canary.22 - 2024-03-14
  • 14.2.0-canary.21 - 2024-03-13
  • 14.2.0-canary.20 - 2024-03-13
  • 14.2.0-canary.19 - 2024-03-12
  • 14.2.0-canary.18 - 2024-03-12
  • 14.2.0-canary.17 - 2024-03-12
  • 14.2.0-canary.16 - 2024-03-11
  • 14.2.0-canary.15 - 2024-03-11
  • 14.2.0-canary.14 - 2024-03-11
  • 14.2.0-canary.13 - 2024-03-10
  • 14.2.0-canary.12 - 2024-03-09
  • 14.2.0-canary.11 - 2024-03-08
  • 14.2.0-canary.10 - 2024-03-08
  • 14.2.0-canary.9 - 2024-03-08
  • 14.2.0-canary.8 - 2024-03-07
  • 14.2.0-canary.7 - 2024-03-07
  • 14.2.0-canary.6 - 2024-03-06
  • 14.2.0-canary.5 - 2024-03-06
  • 14.2.0-canary.4 - 2024-03-06
  • 14.2.0-canary.3 - 2024-03-06
  • 14.2.0-canary.2 - 2024-03-05
  • 14.2.0-canary.1 - 2024-03-05
  • 14.2.0-canary.0 - 2024-03-05
  • 14.1.4 - 2024-03-20
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.
  • Snyk has automatically assigned this pull request, set who gets assigned.

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 14.1.4 to 14.2.10.

See this package in npm:
next

See this project in Snyk:
https://app.snyk.io/org/lryanle/project/5b60c99c-75ea-4ce3-8b20-9bfefab000f5?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Oct 3, 2024

Deployment failed with the following error:

The value for maxDuration must be between 1 second and 60 seconds, in order to increase this limit upgrade your plan: https://vercel.com/pricing

@lryanle lryanle self-assigned this Oct 3, 2024
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