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.

Sign up for GitHub

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

Jump to bottom

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

Closed
wants to merge 1 commit into from
Closed

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 17, 2023 •
edited
Loading

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
react-i18next 11.14.3 -> 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 these updates 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 17, 2023 •
edited
Loading

⚠ 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: 2022/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: jsconfjp-2022@undefined
npm ERR! Found: i18next@22.5.0
npm ERR! node_modules/i18next
npm ERR!   i18next@"22.5.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer i18next@">= 23.2.3" from react-i18next@13.5.0
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/79fe5a/b3a94a/cache/others/npm/_logs/2023-11-15T22_18_11_784Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/79fe5a/b3a94a/cache/others/npm/_logs/2023-11-15T22_18_11_784Z-debug-0.log
File name: 2021/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: jsconfjp-2021@undefined
npm ERR! Found: i18next@21.5.4
npm ERR! node_modules/i18next
npm ERR!   i18next@"21.5.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer i18next@">= 23.2.3" from react-i18next@13.5.0
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/79fe5a/b3a94a/cache/others/npm/_logs/2023-11-15T22_18_22_112Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/79fe5a/b3a94a/cache/others/npm/_logs/2023-11-15T22_18_22_112Z-debug-0.log

@netlify
Copy link

netlify bot commented Jun 17, 2023 •
edited
Loading

✅ Deploy Preview for jsconf-jp-preview ready!

Name Link
🔨 Latest commit 4d25fac
🔍 Latest deploy log https://app.netlify.com/sites/jsconf-jp-preview/deploys/655543b79cdbf3000916be3f
😎 Deploy Preview https://deploy-preview-335--jsconf-jp-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch from 2682e33 to 16b2cf6 Compare June 22, 2023 08:37
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch from 16b2cf6 to 0d524d4 Compare July 10, 2023 19:47
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch from 0d524d4 to a97158e Compare July 31, 2023 14:19
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch 3 times, most recently from 3ba2a1a to bb70043 Compare August 11, 2023 15:16
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch 2 times, most recently from 418284d to 6eaecae Compare August 29, 2023 15:26
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch from 6eaecae to 01c82a8 Compare September 3, 2023 08:06
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch 3 times, most recently from 2edaeca to b6b316c Compare October 19, 2023 18:16
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch 3 times, most recently from 283e6db to ec7513c Compare November 13, 2023 13:54
@renovate renovate bot force-pushed the renovate/react-i18next-13.x branch from ec7513c to 4d25fac 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 16:10
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants