[Snyk] Upgrade sharp from 0.29.3 to 0.34.1

[X-oss-byte]

Snyk has created this PR to upgrade sharp from 0.29.3 to 0.34.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 47 versions ahead of your current version.

• The recommended version was released 22 days ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Remote Code Execution (RCE) SNYK-JS-SHARP-2848109	539	No Known Exploit
	Heap-based Buffer Overflow SNYK-JS-SHARP-5922108	539	Mature

Release notes

Package name: sharp

• 0.34.1 - 2025-04-07
  No content.
• 0.34.0 - 2025-04-04
  No content.
• 0.34.0-rc.1 - 2025-04-03
  No content.
• 0.34.0-rc.0 - 2025-03-16
  No content.
• 0.33.5 - 2024-08-16
  No content.
• 0.33.5-rc.1 - 2024-08-14
  No content.
• 0.33.5-rc.0 - 2024-08-13
  No content.
• 0.33.4 - 2024-05-16
  No content.
• 0.33.4-rc.0 - 2024-05-16
  No content.
• 0.33.3 - 2024-03-23
  No content.
• 0.33.3-rc.0 - 2024-03-22
• 0.33.2 - 2024-01-12
• 0.33.2-rc.1 - 2024-01-12
• 0.33.2-rc.0 - 2024-01-11
• 0.33.1 - 2023-12-17
• 0.33.1-rc.3 - 2023-12-17
• 0.33.1-rc.2 - 2023-12-17
• 0.33.1-rc.0 - 2023-12-12
• 0.33.0 - 2023-11-29
• 0.33.0-rc.2 - 2023-11-22
• 0.33.0-alpha.11 - 2023-11-10
• 0.33.0-alpha.10 - 2023-11-04
• 0.33.0-alpha.9 - 2023-10-13
• 0.33.0-alpha.8 - 2023-10-10
• 0.33.0-alpha.7 - 2023-10-10
• 0.33.0-alpha.6 - 2023-10-09
• 0.33.0-alpha.4 - 2023-10-06
• 0.33.0-alpha.3 - 2023-10-06
• 0.32.6 - 2023-09-18
• 0.32.5 - 2023-08-15
• 0.32.4 - 2023-07-21
• 0.32.3 - 2023-07-14
• 0.32.2 - 2023-07-11
• 0.32.1 - 2023-04-27
• 0.32.0 - 2023-03-24
• 0.31.3 - 2022-12-21
• 0.31.2 - 2022-11-04
• 0.31.1 - 2022-09-29
• 0.31.0 - 2022-09-05
• 0.30.7 - 2022-06-22
• 0.30.6 - 2022-05-30
• 0.30.5 - 2022-05-23
• 0.30.4 - 2022-04-18
• 0.30.3 - 2022-03-14
• 0.30.2 - 2022-03-02
• 0.30.1 - 2022-02-09
• 0.30.0 - 2022-02-01
• 0.29.3 - 2021-11-14

from sharp 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.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

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
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Upgrade the sharp dependency from version 0.29.3 to 0.34.1 to address security vulnerabilities

Bug Fixes:

• Resolve Remote Code Execution vulnerability
• Fix Heap-based Buffer Overflow security issue

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
next-js-next-plugin-storybook	❌ Failed (Inspect)			Apr 29, 2025 2:21pm
next-js-next-plugin-storybook-g5dx	❌ Failed (Inspect)			Apr 29, 2025 2:21pm
next-js-next-plugin-storybook-y5ka	❌ Failed (Inspect)			Apr 29, 2025 2:21pm
next-x-storybook	❌ Failed (Inspect)			Apr 29, 2025 2:21pm

[vercel]

Deployment failed with the following error:

Could not parse File as JSON: vercel.json

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sourcery-ai]

Reviewer's Guide

This pull request upgrades the sharp dependency from version 0.29.3 to 0.34.1 by modifying the version specified in the package.json file.

File-Level Changes

Change	Details	Files
Upgraded sharp dependency version.	Changed the version of sharp from 0.29.3 to 0.34.1.	examples/cms-buttercms/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c230cbb

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