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 gatsby-plugin-sharp from 5.0.0 to 5.13.1 #923

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

Conversation

X-oss-byte
Copy link
Owner

Snyk has created this PR to upgrade gatsby-plugin-sharp from 5.0.0 to 5.13.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 49 versions ahead of your current version.
  • The recommended version was released 9 months ago, on 2024-01-23.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Information Exposure
SNYK-JS-GATSBYPLUGINSHARP-5425803
429/1000
Why? Has a fix available, CVSS 4.3
No Known Exploit
Information Exposure
SNYK-JS-GATSBYPLUGINSHARP-5671648
429/1000
Why? Has a fix available, CVSS 4.3
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-SIDEWAYFORMULA-3317169
429/1000
Why? Has a fix available, CVSS 4.3
No Known Exploit

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

Release notes
Package name: gatsby-plugin-sharp
  • 5.13.1 - 2024-01-23
  • 5.13.0 - 2023-12-18
  • 5.13.0-next.1 - 2023-11-16
  • 5.13.0-next.0 - 2023-07-25
  • 5.13.0-alpha-alt-image-cdn.44 - 2023-11-03
  • 5.12.3 - 2023-10-26
  • 5.12.2 - 2023-10-20
  • 5.12.1 - 2023-10-09
  • 5.12.0 - 2023-08-24
  • 5.12.0-next.1 - 2023-07-03
  • 5.12.0-next.0 - 2023-06-15
  • 5.11.0 - 2023-06-15
  • 5.11.0-next.1 - 2023-06-05
  • 5.11.0-next.0 - 2023-05-16
  • 5.10.0 - 2023-05-16
  • 5.10.0-next.2 - 2023-05-03
  • 5.10.0-next.1 - 2023-04-27
  • 5.10.0-next.0 - 2023-04-18
  • 5.9.0 - 2023-04-18
  • 5.9.0-next.2 - 2023-04-06
  • 5.9.0-next.1 - 2023-03-30
  • 5.9.0-next.0 - 2023-03-21
  • 5.9.0-image-cdn-configurable.4 - 2023-04-11
  • 5.8.1 - 2023-03-29
  • 5.8.0 - 2023-03-21
  • 5.8.0-next.0 - 2023-02-16
  • 5.7.0 - 2023-02-21
  • 5.7.0-next.0 - 2023-02-03
  • 5.6.0 - 2023-02-07
  • 5.6.0-next.1 - 2023-01-26
  • 5.6.0-next.0 - 2023-01-19
  • 5.5.0 - 2023-01-24
  • 5.5.0-next.1 - 2023-01-17
  • 5.5.0-next.0 - 2023-01-05
  • 5.4.0 - 2023-01-10
  • 5.4.0-next.2 - 2023-01-04
  • 5.4.0-next.1 - 2022-12-14
  • 5.4.0-next.0 - 2022-12-08
  • 5.3.2 - 2022-12-14
  • 5.3.1 - 2022-12-14
  • 5.3.0 - 2022-12-13
  • 5.3.0-next.3 - 2022-12-07
  • 5.3.0-next.2 - 2022-12-06
  • 5.3.0-next.1 - 2022-12-01
  • 5.3.0-next.0 - 2022-11-25
  • 5.2.0 - 2022-11-25
  • 5.2.0-next.0 - 2022-11-17
  • 5.1.0 - 2022-11-22
  • 5.1.0-next.0 - 2022-11-08
  • 5.0.0 - 2022-11-08
from gatsby-plugin-sharp GitHub release notes
Commit messages
Package name: gatsby-plugin-sharp

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

Copy link

stackblitz bot commented Oct 17, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

changeset-bot bot commented Oct 17, 2024

⚠️ No Changeset found

Latest commit: 718d37e

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.

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

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

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