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

chore(deps): update dependency react-i18next to v15 #6263

Open
wants to merge 1 commit into
base: master
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 ^12.3.1 -> ^15.0.0 age adoption passing confidence

Release Notes

i18next/react-i18next (react-i18next)

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))

v14.1.3

Compare Source

  • create a isObject helper function 1766
  • optimize nodesToString 1765
  • Simplifies hasValidReactChildren 1764
  • create a isString helper to avoid code duplication 1763
  • use arrow functions where possible 1762
  • use the commented out async code 1761

v14.1.2

Compare Source

  • bring back internal interpolationOverride handling for Trans component (if there are childrens), fixes 1754

v14.1.1

Compare Source

  • do not modify passed tOptions context property to address 1745

v14.1.0

Compare Source

  • types(Trans): add typechecking on context prop 1732 (might brake if using "internal" Trans or TransProps)

v14.0.8

Compare Source

  • fix: issue 1728 when useSuspense is false and default ns 1731

v14.0.7

Compare Source

  • try to get rid of internal interpolationOverride handling for Trans component, fixes 1729

v14.0.6

Compare Source

  • align context handling of Trans component with t function, fixes 1729

v14.0.5

Compare Source

  • Fix 1691 for strict mode, by preserving change language binding 1720

v14.0.4

Compare Source

  • fix interpolation of the count prop 1719

v14.0.3

Compare Source

  • revert changes done in v14.0.2 since it breaks normal language change render updates

v14.0.2

Compare Source

  • Fix/bug 1691 make returned t function identical upon second effect run in strict mode 1716

v14.0.1

Compare Source

  • types: fix typo in CustomInstanceExtensions 1713

v14.0.0

Compare Source

  • types: reportNamespaces is now optional, should fix 1693

v13.5.0

Compare Source

  • self-closing components in translation strings should not attempt to replace the component's children 1695

v13.4.1

Compare Source

  • types: use CustomInstanceExtenstions to extend reportNamespaces

v13.4.0

Compare Source

  • fix: separate cjs and mjs typings

v13.3.2

Compare Source

  • types: fix consider importing '*.js'

v13.3.1

Compare Source

  • optimize defaultVariables feature introduced in last release

v13.3.0

Compare Source

  • Respect defaultVariables in the interpolation options 1685

v13.2.2

Compare Source

  • Fix missing TransWithoutContext type 1672

v13.2.1

Compare Source

  • types: Allow iterable ReactI18NextChildren as children 1669

v13.2.0

Compare Source

  • Don't use defaults prop as default key 1664

v13.1.2

Compare Source

  • postpone usage of newer ES syntax

v13.1.1

Compare Source

  • Render all children regardless of type when using i18nIsDynamicList prop 1661

v13.1.0

Compare Source

  • Fix non-list dynamic content in Trans component 1660

v13.0.3

Compare Source

  • fix unescape is not consistently called for all values 1657

v13.0.2

Compare Source

  • export icu.macro 1652

v13.0.1

Compare Source

  • types: Fix performance issue in Trans component 1646

v13.0.0

Compare Source

  • Update types to support t function redesign 1615
  • requires i18next >= v23.0.1

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.

Copy link

github-actions bot commented Jul 17, 2024

COMPARE TO master

Total Size Diff 0 Bytes

Diff by File
Name Diff
packages/console/package.json 0 Bytes
packages/demo-app/package.json 0 Bytes
packages/experience-legacy/package.json 0 Bytes
packages/experience/package.json 0 Bytes
pnpm-lock.yaml 0 Bytes

@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch 2 times, most recently from 067f5ec to 3df4657 Compare July 22, 2024 03:08
Copy link

github-actions bot commented Aug 7, 2024

This PR is stale because it has been open 10 for days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Aug 7, 2024
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch from 3df4657 to 9c6a098 Compare August 27, 2024 04:41
@github-actions github-actions bot removed the stale label Sep 3, 2024
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch 4 times, most recently from a82bd2b to 40be990 Compare September 9, 2024 09:13
@renovate renovate bot force-pushed the renovate/react-i18next-15.x branch from 40be990 to ddb0a2e Compare October 15, 2024 05:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

0 participants