Update dependency next-intl to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
next-intl (source)	^3.26.3 -> ^4.0.0

---

Release Notes

amannn/next-intl (next-intl)

v4.5.5

Compare Source

Bug Fixes

• Move SWC cache to node_modules (#​2120) (0ba9105) – by @​amannn

v4.5.4

Compare Source

Bug Fixes

• Move AST transformer of useExtracted to SWC plugin & handle source maps (#​2114) (e63fbc5) – by @​amannn

v4.5.3

Compare Source

Bug Fixes

• Fix inconsistent ordering of messages for useExtracted pt. 2 (#​2103) (5cbd5da) – by @​amannn

v4.5.2

Compare Source

Bug Fixes

• Bug fixes for useExtracted (#​2099) (b1ff1fa) – by @​amannn

v4.5.1

Compare Source

Bug Fixes

• Avoid partial matches in overlapping localized pathnames (#​2090) (c276c80), closes #​2089 #​2089 – by @​amannn

v4.5.0

Compare Source

Features

• Add useExtracted (experimental) (#​2080) (7a85644) – by @​amannn

v4.4.0

Compare Source

Features

• Next.js 16 update (#​2054) (c397e92) – by @​amannn

v4.3.12

Compare Source

Bug Fixes

• Use correct return type for getTimeZone (#​2053) (bdc2af4), closes #​2052 – by @​amannn

v4.3.11

Compare Source

Bug Fixes

• Only call NextResponse.rewrite if really necessary (#​2051) (43ed4aa) – by @​amannn

v4.3.10

Compare Source

Bug Fixes

• Bump @types/react version (#​2050) (c1e997e), closes #​2044 #​2044 – by @​amannn

v4.3.9

Compare Source

Bug Fixes

• Prefix pathnames when switching with useRouter to another locale (#​2021) (c82d0af), closes #​2020 – by @​amannn

v4.3.8

Compare Source

Bug Fixes

• Avoid double-encoding of already encoded params (#​2017) (31265b4), closes #​2014 – by @​amannn

v4.3.7

Compare Source

Bug Fixes

• Avoid usePathname inconsistency in Next.js leading to a hydration error with custom prefixes, localePrefix: 'always' and static rendering (#​2012) (bc9cb62), closes #​2011 vercel/next.js#73085 #​1571 – by @​hugotiger

v4.3.6

Compare Source

Bug Fixes

• Ensure messages declaration continues working in next dev for upcoming [email protected] (#​2008) (2bf09ec) – by @​amannn

v4.3.5

Compare Source

Bug Fixes

• Don't create messages declaration file when running next {start,info,telemetry} (#​1992) (fd0722a) – by @​amannn

v4.3.4

Compare Source

Bug Fixes

• Correctly compile messages containing escaped curly braces (e.g. '{name'}) (#​1950) (4d418f4), closes #​1948 – by @​amannn

v4.3.3

Compare Source

Bug Fixes

• Add friendly error message when failing to load current Next.js version (#​1945) (5021773) – by @​cupofjoakim

v4.3.2

Compare Source

Bug Fixes

• Ensure cookie is synced before navigation with useRouter (#​1947) (3ee9c4d) – by @​amannn

v4.3.1

Compare Source

Bug Fixes

• Use correct return type for getTimeZone (#​2053) (bdc2af4), closes #​2052 – by @​amannn

v4.3.0

Compare Source

Features

• Support BigInt for number interpolation with useTranslations (#​1929) (a893330), closes #​1928 – by @​sgleisner

v4.2.0

Compare Source

Features

• Encode non-ASCII characters in pathnames returned from navigation APIs (#​1923) (3d23c61) – by @​amannn

v4.1.0

Compare Source

Features

• Add forcePrefix option for redirect and getPathname (#​1865) (5905976) – by @​amannn

v4.0.3

Compare Source

Features

• Experimental support for --turbo (requires next@^14.0.3) (#​641) (46c6ec7), closes #​250

3.0.3 (2023-11-15)

Bug Fixes

• Don't retrieve defaults for locale, now and timeZone if these options have been provided to NextIntlClientProvider (#​633) (824363a), closes #​631

3.0.2 (2023-11-15)

Bug Fixes

• Allow usage of getTranslations({namespace}) without TypeScript integration for messages (#​630) (62cf29c), closes #​625

3.0.1 (2023-11-14)

Add provenance statement to published packages.

v4.0.2

Compare Source

Bug Fixes

• Allow to use IntlErrorCode in user code (#​1788) (913d307), closes #​1787 – by @​amannn

v4.0.1

Compare Source

Bug Fixes

• Handle default exports correctly for moduleResolution: 'node' (#​1785) (b7a4a83), closes /github.com/amannn/next-intl/discussions/1631#discussioncomment-12477848 – by @​amannn

v4.0.0

Compare Source

See the announcement.

(#​1412) (172656f) – by @​amannn

v3.26.5

Compare Source

Bug Fixes

• Handle query in <Link /> correctly when using localePrefix: 'as-needed' with domains (#​1732) (ec8776e), closes #​1731 – by @​amannn

v3.26.4

Compare Source

Bug Fixes

• Add workaround for OpenTelemetry/Zone.js (#​1719) (1cac9a6), closes #​1711 – by @​amannn

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @headlessui/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^19.0.0" from the root project
npm error   peer react@">=16.8.0" from @floating-ui/[email protected]
npm error   node_modules/@floating-ui/react-dom
npm error     @floating-ui/react-dom@"^2.0.0" from @radix-ui/[email protected]
npm error     node_modules/@radix-ui/react-popper
npm error       @radix-ui/react-popper@"1.2.0" from @radix-ui/[email protected]
npm error       node_modules/@radix-ui/react-select
npm error         @radix-ui/react-select@"^2.0.0" from the root project
npm error   53 more (@radix-ui/react-accordion, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16 || ^17 || ^18" from @headlessui/[email protected]
npm error node_modules/@headlessui/react
npm error   @headlessui/react@"^1.7.18" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16 || ^17 || ^18" from @headlessui/[email protected]
npm error   node_modules/@headlessui/react
npm error     @headlessui/react@"^1.7.18" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-11-19T14_49_24_156Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-19T14_49_24_156Z-debug-0.log

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
aurora-web	Ready	Preview	Comment	Nov 19, 2025 2:54pm

[cloudflare-workers-and-pages]

Deploying aurora-web with    Cloudflare Pages

Latest commit:	d1b6cb2
Status:	🚫  Build failed.

View logs