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 i18next to v22 #40

Merged
merged 7 commits into from Oct 24, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 19, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
i18next (source) ^21.10.0 -> ^22.0.2 age adoption passing confidence

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: Renovate will not automatically rebase this PR, because other commits have been found.

πŸ”• Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

This PR has been generated by Mend Renovate. View repository job log here.

@erik-slovak
Copy link
Contributor

erik-slovak commented Oct 19, 2022

@renovate renovate bot force-pushed the renovate/i18next-22.x branch 4 times, most recently from 4fab861 to 2e17d0c Compare October 21, 2022 05:20
@rostislav-simonik rostislav-simonik merged commit 72469de into main Oct 24, 2022
@rostislav-simonik rostislav-simonik deleted the renovate/i18next-22.x branch October 24, 2022 07:25
rostislav-simonik pushed a commit that referenced this pull request Oct 24, 2022
## [3.0.2](v3.0.1...v3.0.2) (2022-10-24)

### Bug fixes

* **deps:** update dependency i18next to v22 ([#40](#40)) ([72469de](72469de))
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.

None yet

2 participants