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

[Snyk] Upgrade i18next-http-backend from 2.2.0 to 2.4.1 #14

Merged
merged 1 commit into from
Dec 15, 2023

Conversation

Niraj-Dilshan
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade i18next-http-backend from 2.2.0 to 2.4.1.

ℹ️ 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 6 versions ahead of your current version.
  • The recommended version was released 22 days ago, on 2023-11-10.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: i18next-http-backend from i18next-http-backend GitHub release notes
Commit messages
Package name: i18next-http-backend

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@Niraj-Dilshan Niraj-Dilshan merged commit 5eda990 into master Dec 15, 2023
@Niraj-Dilshan Niraj-Dilshan deleted the snyk-upgrade-b72ad13df93d34e5ead344994cc8720f branch December 15, 2023 04:22
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.

2 participants