Skip to content

chore: 🤖 update dependency react-i18next to v11.18.6#6

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/react-i18next-11.x
Open

chore: 🤖 update dependency react-i18next to v11.18.6#6
renovate[bot] wants to merge 1 commit intomainfrom
renovate/react-i18next-11.x

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented May 6, 2022

This PR contains the following updates:

Package Change Age Confidence
react-i18next 11.16.811.18.6 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

i18next/react-i18next (react-i18next)

v11.18.6

Compare Source

  • types: nsMode 1554

v11.18.5

Compare Source

  • support unescaping forward slash 1548

v11.18.4

Compare Source

  • fix: reset t when keyPrefix is updated 1544

v11.18.3

Compare Source

  • types: bindI18n option for UseTranslationOptions

v11.18.2

Compare Source

  • more html entities to unescape by default 1538

v11.18.1

Compare Source

  • types: allow iterable with objects as children 1531

v11.18.0

Compare Source

  • ability to add custom unescape function 1529

v11.17.4

Compare Source

  • fix: UMD build 1527

v11.17.3

Compare Source

  • style: explicit React imports 1525

v11.17.2

Compare Source

  • reset t if ns changes in useTranslation 1518

v11.17.1

Compare Source

  • Stricter typescript type for Trans components prop 1516

v11.17.0

Compare Source

  • Add support for keyPrefix in withTranslation 1512

v11.16.11

Compare Source

  • types: fix Translation component types regression 1511

v11.16.10

Compare Source

  • types: translation component types 1509

v11.16.9

Compare Source

  • types: fix missing generic type for HTMLAttributes 1499

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 force-pushed the renovate/react-i18next-11.x branch from 99bc7f6 to 4d704f2 Compare June 3, 2022 06:26
@renovate renovate bot changed the title chore: 🤖 update dependency react-i18next to v11.16.9 chore: 🤖 update dependency react-i18next to v11.16.10 Jun 3, 2022
@renovate renovate bot force-pushed the renovate/react-i18next-11.x branch from 4d704f2 to 8be5803 Compare June 3, 2022 12:40
@renovate renovate bot changed the title chore: 🤖 update dependency react-i18next to v11.16.10 chore: 🤖 update dependency react-i18next to v11.16.11 Jun 3, 2022
@renovate renovate bot force-pushed the renovate/react-i18next-11.x branch from 8be5803 to b8f590d Compare June 3, 2022 15:31
@renovate renovate bot changed the title chore: 🤖 update dependency react-i18next to v11.16.11 chore: 🤖 update dependency react-i18next to v11.17.0 Jun 3, 2022
@renovate renovate bot force-pushed the renovate/react-i18next-11.x branch from b8f590d to 8e0c333 Compare June 10, 2022 06:57
@renovate renovate bot changed the title chore: 🤖 update dependency react-i18next to v11.17.0 chore: 🤖 update dependency react-i18next to v11.17.1 Jun 10, 2022
@renovate renovate bot changed the title chore: 🤖 update dependency react-i18next to v11.17.1 chore: 🤖 update dependency react-i18next to v11.17.2 Jun 14, 2022
@renovate renovate bot force-pushed the renovate/react-i18next-11.x branch from 8e0c333 to 957f80a Compare June 14, 2022 22:13
@renovate renovate bot force-pushed the renovate/react-i18next-11.x branch from 957f80a to b95c3e3 Compare June 26, 2022 21:51
@renovate renovate bot changed the title chore: 🤖 update dependency react-i18next to v11.17.2 chore: 🤖 update dependency react-i18next to v11.17.3 Jun 26, 2022
@renovate renovate bot changed the title chore: 🤖 update dependency react-i18next to v11.17.3 chore: 🤖 Update dependency react-i18next to v11.17.3 Jun 27, 2022
@renovate renovate bot changed the title chore: 🤖 Update dependency react-i18next to v11.17.3 chore: 🤖 update dependency react-i18next to v11.17.3 Jun 28, 2022
@renovate renovate bot force-pushed the renovate/react-i18next-11.x branch from b95c3e3 to a243561 Compare June 30, 2022 16:59
@renovate renovate bot changed the title chore: 🤖 update dependency react-i18next to v11.17.3 chore: 🤖 update dependency react-i18next to v11.17.4 Jun 30, 2022
@renovate renovate bot force-pushed the renovate/react-i18next-11.x branch from a243561 to dc174a5 Compare July 6, 2022 10:31
@renovate renovate bot changed the title chore: 🤖 update dependency react-i18next to v11.17.4 chore: 🤖 update dependency react-i18next to v11.18.0 Jul 6, 2022
@renovate renovate bot force-pushed the renovate/react-i18next-11.x branch from dc174a5 to 2fc4f6e Compare September 25, 2022 15:57
@renovate renovate bot changed the title chore: 🤖 update dependency react-i18next to v11.18.0 chore: 🤖 update dependency react-i18next to v11.18.6 Sep 25, 2022
@renovate renovate bot force-pushed the renovate/react-i18next-11.x branch from 2fc4f6e to 15687c1 Compare August 12, 2025 00:11
@renovate
Copy link
Copy Markdown
Author

renovate bot commented Aug 12, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact 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: pnpm-lock.yaml
(node:1779) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)

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