Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

fix(deps): update dependency react-i18next to v13 - autoclosed #59

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 15, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-i18next 12.3.1 -> 13.5.0 age adoption passing confidence

Release Notes

i18next/react-i18next (react-i18next)

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 has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Jun 15, 2023

⚠ Artifact update problem

Renovate failed to update artifacts 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: storefront/package-lock.json
npm WARN cli npm v10.2.4 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN cli npm v10.2.4 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/i18next
npm ERR!   i18next@"22.5.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer i18next@">= 23.2.3" from [email protected]
npm ERR! node_modules/react-i18next
npm ERR!   react-i18next@"13.5.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/b717ac/5f29c8/cache/others/npm/_logs/2023-11-15T22_18_08_617Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/b717ac/5f29c8/cache/others/npm/_logs/2023-11-15T22_18_08_617Z-debug-0.log

File name: firebase/functions/package-lock.json
npm WARN cli npm v10.2.4 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN cli npm v10.2.4 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: functions@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/i18next
npm ERR!   i18next@"22.5.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer i18next@">= 23.2.3" from [email protected]
npm ERR! node_modules/react-i18next
npm ERR!   react-i18next@"13.5.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/b717ac/5f29c8/cache/others/npm/_logs/2023-11-15T22_18_16_657Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/b717ac/5f29c8/cache/others/npm/_logs/2023-11-15T22_18_16_657Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch from b4a34d6 to 1010f64 Compare June 22, 2023 06:52
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch from 1010f64 to 633d950 Compare July 10, 2023 19:54
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch from 633d950 to 332f555 Compare July 31, 2023 14:47
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch 3 times, most recently from 7eb864d to ffe61d5 Compare August 11, 2023 15:56
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch 2 times, most recently from 1594c20 to be7ee0e Compare August 29, 2023 17:02
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch from be7ee0e to d5f6941 Compare September 3, 2023 08:26
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch 2 times, most recently from e6489d5 to 0f2b674 Compare October 19, 2023 15:38
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch 3 times, most recently from 1938f6f to 4db90b6 Compare November 13, 2023 14:07
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch from 4db90b6 to 55fa0aa Compare November 15, 2023 22:18
@renovate renovate bot changed the title fix(deps): update dependency react-i18next to v13 fix(deps): update dependency react-i18next to v13 - autoclosed Dec 21, 2023
@renovate renovate bot closed this Dec 21, 2023
@renovate renovate bot deleted the renovate/react-i18next-13.x branch December 21, 2023 15:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants