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

fix(deps): update dependency i18next to v23.9.0 #501

Merged
merged 1 commit into from
Feb 21, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
i18next (source) 23.8.2 -> 23.9.0 age adoption passing confidence

Release Notes

i18next/i18next (i18next)

v23.9.0

Compare Source

  • types: support nested keys in InterpolationMap 2140 fixes 2014

v23.8.3

Compare Source

  • prevent resource mutation when using addResourceBundle 2081

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC).

🚦 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 renovate bot added the dependencies Pull requests that update a dependency file label Feb 5, 2024
@renovate renovate bot force-pushed the renovate/i18next-23.x branch 3 times, most recently from b220cff to 6a19190 Compare February 9, 2024 08:57
@renovate renovate bot force-pushed the renovate/i18next-23.x branch 8 times, most recently from 657e6fc to 9e2a78e Compare February 16, 2024 14:12
@renovate renovate bot changed the title fix(deps): update dependency i18next to v23.8.2 fix(deps): update dependency i18next to v23.8.2 - autoclosed Feb 16, 2024
@renovate renovate bot closed this Feb 16, 2024
@renovate renovate bot deleted the renovate/i18next-23.x branch February 16, 2024 14:55
@renovate renovate bot changed the title fix(deps): update dependency i18next to v23.8.2 - autoclosed fix(deps): update dependency i18next to v23.8.2 Feb 18, 2024
@renovate renovate bot reopened this Feb 18, 2024
@renovate renovate bot restored the renovate/i18next-23.x branch February 18, 2024 16:58
@renovate renovate bot changed the title fix(deps): update dependency i18next to v23.8.2 fix(deps): update dependency i18next to v23.9.0 Feb 18, 2024
Copy link

sonarcloud bot commented Feb 18, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@spaenleh spaenleh added this pull request to the merge queue Feb 21, 2024
Copy link
Contributor Author

renovate bot commented Feb 21, 2024

⚠ 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: yarn.lock
Internal Error: ENOENT: no such file or directory, open '/home/ubuntu/.cache/node/corepack/lastKnownGood.json'
Error: ENOENT: no such file or directory, open '/home/ubuntu/.cache/node/corepack/lastKnownGood.json'

Merged via the queue into main with commit 642d359 Feb 21, 2024
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file v2.5.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant