Skip to content

Conversation

@KevinOomenTheDeveloper
Copy link
Member

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


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade next from 14.2.3 to 14.2.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 1 version ahead of your current version.

  • The recommended version was released on 21 days ago.

Release notes
Package name: next
  • 14.2.4 - 2024-06-11

    Note

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

    Core Changes

    • fix: ensure route handlers properly track dynamic access (#66446)
    • fix NextRequest proxy in edge runtime (#66551)
    • Fix next/dynamic with babel and src dir (#65177)
    • Use vercel deployment url for metadataBase fallbacks (#65089)
    • fix(next/image): detect react@19 for fetchPriority prop (#65235)
    • Fix loading navigation with metadata and prefetch (#66447)
    • prevent duplicate RSC fetch when action redirects (#66620)
    • ensure router cache updates reference the latest cache values (#66681)
    • Prevent append of trailing slash in cases where path ends with a file extension (#66636)
    • Fix inconsistency with 404 getStaticProps cache-control (#66674)
    • Use addDependency to track metadata route file changes (#66714)
    • Add timeout/retry handling for fetch cache (#66652)
    • fix: app-router prefetch crash when an invalid URL is passed to Link (#66755)

    Credits

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

  • 14.2.3 - 2024-04-24
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:

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