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

fix(deps): update dependency i18next to v24 #1028

Merged
merged 1 commit into from
Nov 23, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 22, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
i18next (source) ^23.11.5 -> ^24.0.0 age adoption passing confidence

Release Notes

i18next/i18next (i18next)

v24.0.0

Compare Source

This is a major breaking release:

  • remove support for older environments
  • remove old i18next JSON formats
  • remove support for compatibility to v1 API
  • Intl API is mandatory now and will not fallback anymore
  • possible compatibility layer for older formats: test/compatibility/v4/v4Compatibility.js
  • rename initImmediate to initAsync
  • fallback to dev language if plural rule not found
  • remove TypeScript v4 support. TypeScript v5 is now an optional peer dependency
  • addresses

➡️ check out the migration guide


Configuration

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

🚦 Automerge: Enabled.

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 renovate bot merged commit 28ac5e9 into dev Nov 23, 2024
6 checks passed
@renovate renovate bot deleted the renovate/i18next-24.x branch November 23, 2024 01:42
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.

0 participants