[Snyk] Upgrade next-intl from 3.3.1 to 3.4.2

[Woodpile37]

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

Snyk has created this PR to upgrade next-intl from 3.3.1 to 3.4.2.

ℹ️ 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 5 versions ahead of your current version.
• The recommended version was released 25 days ago, on 2024-01-09.

Release notes

Package name: next-intl

• 3.4.2 - 2024-01-09
  

  v3.4.2

• 3.4.1 - 2024-01-03
  

  v3.4.1

• 3.4.0 - 2023-12-21
  

  v3.4.0

• 3.3.3 - 2023-12-20
  

  v3.3.3

• 3.3.2 - 2023-12-11
  

  v3.3.2

• 3.3.1 - 2023-12-07
  

  v3.3.1

from next-intl GitHub release notes

Commit messages

Package name: next-intl

• 2ea59f6 v3.4.2
• 246d373 fix: Change `numeric` option from `auto` to `always` for `format.relativeTime` (Add weekly update 2016-05-30 nodejs/nodejs.org#765)
• e90eda6 v3.4.1
• e73fb38 fix: Fix ESM output of `use-intl` (Add missing fields to the Italian site.json nodejs/nodejs.org#754)
• f8cdcf2 docs: Improve showcase layout (foundation: update sauce logo nodejs/nodejs.org#751)
• 256b232 docs: Remove links to Bundlephobia since it's broken
• 0301f0b docs: Wording for support
• 8e887d5 docs: Add link to support in bug report template
• 32ce768 docs: Add link in GitHub issues for paid support
• 75d1158 docs: Improve showcase layout (optimize png images losslessly using zopflipng nodejs/nodejs.org#746)
• 96144a3 docs: Add missing imports (add v6.2.0 release post nodejs/nodejs.org#747)
• 9ec08bb docs: Add code example for how to upgrade `NextIntlClientProvider` in 3.0 in App Router
• 7729a01 docs: Add note to rewrite example about `localePrefix` (closes Update some dependencies to their latest version nodejs/nodejs.org#737)
• 7f87617 v3.4.0
• e6d9878 feat: Invoke `notFound()` when no locale was attached to the request and update docs to suggest validating the locale in `i18n.ts` (Add shasums to download page nodejs/nodejs.org#742)
• b9e17a9 v3.3.3
• 4185a72 fix: Improve performance when calling hooks like `useTranslations` in Server Components by making sure we only suspend when i18n config is initially loaded and never for subsequent calls (nodejs.org API doc mistake？ nodejs/nodejs.org#741)
• 8009a95 docs: Ensure cookie path is set (Evangelism: Weekly Update for May ~ nodejs/nodejs.org#732)
• 1b51799 docs: Update Next.js to 14.0.4 in examples (blog: Update v4.4.4 with arm nodejs/nodejs.org#730)
• b2ce58b docs: Wording
• 4572f96 docs: "Can I customize the alternate links?"
• dbe1927 docs: Add note on how to add redirects for unprefixed requests when using `localePrefix: 'always'`
• 3ff88fd docs: Fix dynamic imports in `example-pages-router-advanced` (Add gzip task for production, fixes #712 nodejs/nodejs.org#713 by @ pockata)
• 6cb5325 v3.3.2

Compare

---

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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 772ed93

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codeautopilot]

PR summary

The Pull Request (PR) aims to upgrade the next-intl package from version 3.3.1 to 3.4.2. This update includes several minor versions and patches that have been released since the current version in use. The upgrade is recommended to keep dependencies up-to-date, which helps in fixing existing vulnerabilities and identifying new ones more quickly. The new version was released 25 days ago, and the PR was automatically created by Snyk, a service that helps with identifying and fixing vulnerabilities in project dependencies.

Suggestion

It is generally a good practice to review the release notes and commit messages to understand the changes introduced with the upgrade. Ensure that the upgrade does not introduce any breaking changes that could affect the current project setup. Additionally, it is advisable to test the application thoroughly after upgrading the dependency to ensure that all functionalities are working as expected.

If the project has a comprehensive test suite, running all tests after the upgrade can provide confidence that the update does not break any existing functionality. If the project lacks sufficient test coverage, consider manually testing critical features that rely on next-intl.

If there are no breaking changes and the upgrade is straightforward, it is recommended to merge the PR after successful testing. If the project has specific versioning policies or requires a more cautious approach to dependency upgrades, consider scheduling the upgrade for a more appropriate time.

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 50.29%

Have feedback or need help?
Discord
Documentation
support@codeautopilot.com

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/next-intl@3.4.2	environment Transitive: filesystem, network, shell, unsafe	+41	1.16 GB	amann

🚮 Removed packages: npm/next-intl@3.3.1

View full report↗︎