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 turbo from 1.11.3 to 1.12.2 #29

Closed
wants to merge 1 commit into from

Conversation

neekolas
Copy link
Contributor

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


Snyk has created this PR to upgrade turbo from 1.11.3 to 1.12.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 8 versions ahead of your current version.
  • The recommended version was released 21 days ago, on 2024-01-31.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
417/1000
Why? Proof of Concept exploit, CVSS 6.2
Proof of Concept

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

Release notes
Package name: turbo from turbo GitHub release notes

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

@neekolas neekolas requested a review from a team February 22, 2024 08:28
Copy link

vercel bot commented Feb 22, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
snap-site ❌ Failed (Inspect) Feb 22, 2024 8:28am

Copy link

changeset-bot bot commented Feb 22, 2024

⚠️ No Changeset found

Latest commit: 171b586

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@rygine
Copy link
Collaborator

rygine commented Feb 22, 2024

going to manually upgrade this dependency in a future PR

@rygine rygine closed this Feb 22, 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.

3 participants