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

Update dependency react-i18next to v15 #270

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 17, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-i18next 14.1.3 -> 15.2.0 age adoption passing confidence

Release Notes

i18next/react-i18next (react-i18next)

v15.2.0

Compare Source

This version may be breaking if you still use React < v18 with TypeScript.
For JS users this version is equal to v15.1.4

  • fix: Global JSX namespace is deprecated 1823 with 1822

v15.1.4

Compare Source

  • Fix: warning each child should have a unique key 1820

v15.1.3

Compare Source

  • fix: Self-closing REACT components in translation strings should not attempt to replace the component's children 1815 1816

v15.1.2

Compare Source

  • fix: Attempted to assign to readonly property 1813

v15.1.1

Compare Source

  • fix: Not all namespaces are loaded when passing the lng option to useTranslate 1809

v15.1.0

Compare Source

  • fix: <Trans /> warns 'Each child in a list should have a unique "key" prop.' for react 19 1806

v15.0.3

Compare Source

v15.0.2

Compare Source

  • try to fix Trans handling with alwaysFormat set to true 1801

v15.0.1

Compare Source

  • revert arrow function in class property to address this

v15.0.0

Compare Source

  • use optional chaining, nullish coalescing and nullish coalescing assignment 1774
  • Build config and optimizations 1769
  • some dependency updates 1768
  • use modern hasLoadedNamespace code (now requires at least i18next > v19.4.5 (introduced in june 2020))

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 3pm every weekday,before 6am every weekday,every weekend" in timezone Europe/Berlin.

🚦 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 renovate bot force-pushed the renovate/react-i18next-15.x branch from ebf141f to bd3773f Compare July 29, 2024 00:36
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch 2 times, most recently from 92ebe78 to 0a68671 Compare August 13, 2024 15:12
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch from 0a68671 to cb13f3c Compare August 26, 2024 01:52
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch from cb13f3c to 589a003 Compare September 2, 2024 16:55
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch from 589a003 to 921acfc Compare September 15, 2024 00:29
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch 2 times, most recently from c56460b to 5afd209 Compare October 12, 2024 19:20
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch 2 times, most recently from 9c0815b to d79a740 Compare October 28, 2024 03:04
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch from d79a740 to 5cd196d Compare November 7, 2024 12:12
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch 2 times, most recently from ca98cbf to 81ef48f Compare November 29, 2024 12:01
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch 2 times, most recently from 3c7ccaf to 73b38b0 Compare December 9, 2024 17:08
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch from 73b38b0 to f060bbe Compare December 12, 2024 16:43
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.

1 participant