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

OPHJOD-851: Upgrade react-i18next from 15.1.1 to 15.2.0 #316

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

snyk-io[bot]
Copy link
Contributor

@snyk-io snyk-io bot commented Dec 20, 2024

Description

Upgrade react-i18next from 15.1.1 to 15.2.0

Related JIRA ticket

https://jira.eduuni.fi/browse/OPHJOD-851

Original snyk message

Snyk has created this PR to upgrade react-i18next from 15.1.1 to 15.1.2

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released 24 days ago.

Release notes
Package name: react-i18next from react-i18next GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

@ketsappi ketsappi self-assigned this Dec 20, 2024
@ketsappi ketsappi force-pushed the snyk-upgrade-86b19dd9fbfb3c1695e57e42a970ad85 branch from 6a4aff7 to 22a274f Compare December 20, 2024 09:29
@ketsappi ketsappi changed the title OPHJOD-851: Upgrade react-i18next from 15.1.1 to 15.1.2 OPHJOD-851: Upgrade react-i18next from 15.1.1 to 15.2.0 Dec 20, 2024
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.

1 participant