fix(deps): update dependency @formatjs/intl to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@formatjs/intl (source)	3.1.6 → 4.1.2

---

Release Notes

formatjs/formatjs (@​formatjs/intl)

v4.1.2

Compare Source

v4.1.1

Compare Source

4.1.1 (2026-01-19)

Bug Fixes

• @​formatjs/intl: remove hot path optimization to fix escaped character handling, fix #​4973 (309f579) - by @​longlho

v4.1.0

Compare Source

4.1.0 (2026-01-15)

Features

• @​formatjs/intl-segmenter: improve Unicode 17.0 Format/Extend transparency and upgrade deps (#​5862) (effeb9c), closes #​29 - by @​longlho

v4.0.9

Compare Source

v4.0.8

Compare Source

v4.0.7

Compare Source

v4.0.6

Compare Source

v4.0.5

Compare Source

v4.0.4

Compare Source

v4.0.2

Compare Source

v4.0.1

Compare Source

v4.0.0

Compare Source

⚠ BREAKING CHANGES

• @​formatjs/ts-transformer: convert to ESM only (#​5208)

Features

• @​formatjs/ts-transformer: convert to ESM only (#​5208) (c00f9f3) - by @​longlho

v3.1.8

Compare Source

Bug Fixes

• remove injectIntl types from component props (#​1415) (9b359ec), closes #​1414

v3.1.7

Compare Source

3.1.7 (2025-10-03)

Bug Fixes

• formatList null value replaced to placeholder value (f629131) - by @​septs
• string list from iterable (#​5046) (19a4c05) - by @​septs

---

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 is behind base branch, 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @formatjs/intl@4.1.2
npm error Found: typescript@5.5.4
npm error node_modules/typescript
npm error   typescript@"5.5.4" from the root project
npm error   peer typescript@">=4.2.0" from ts-api-utils@1.3.0
npm error   node_modules/ts-api-utils
npm error     ts-api-utils@"^1.3.0" from @typescript-eslint/eslint-plugin@7.18.0
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       dev @typescript-eslint/eslint-plugin@"7.18.0" from the root project
npm error     ts-api-utils@"^1.3.0" from @typescript-eslint/type-utils@7.18.0
npm error     node_modules/@typescript-eslint/type-utils
npm error       @typescript-eslint/type-utils@"7.18.0" from @typescript-eslint/eslint-plugin@7.18.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"7.18.0" from the root project
npm error     2 more (@typescript-eslint/typescript-estree, @typescript-eslint/typescript-estree)
npm error   1 more (ts-loader)
npm error
npm error Could not resolve dependency:
npm error peerOptional typescript@"^5.6.0" from @formatjs/intl@4.1.2
npm error node_modules/@formatjs/intl
npm error   @formatjs/intl@"4.1.2" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peerOptional typescript@"^5.6.0" from @formatjs/intl@4.1.2
npm error   node_modules/@formatjs/intl
npm error     @formatjs/intl@"4.1.2" 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/2026-02-03T00_00_14_674Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-03T00_00_14_674Z-debug-0.log