Bump decompress and gatsby-plugin-sharp

[dependabot]

Removes decompress. It's no longer used after updating ancestor dependency gatsby-plugin-sharp. These dependencies need to be updated together.

Removes decompress

Updates gatsby-plugin-sharp from 2.0.5 to 5.16.0

Release notes

Sourced from gatsby-plugin-sharp's releases.

gatsby@5.16.0

What's Changed

• feat: support React 19 by @​serhalp in gatsbyjs/gatsby#39306
• feat: support Node.js 24 by @​serhalp in gatsbyjs/gatsby#39380 and gatsbyjs/gatsby#39398
• fix(deps): bump body-parser to resolve qs vulnerability warning by @​serhalp in gatsbyjs/gatsby#39396
• chore(docs,starters): remove misc. outdated, invalid, or misleading instructions by @​serhalp in gatsbyjs/gatsby#39363

React 19

[!NOTE] 🔐 As of January 26 2026, none of the React 19 security vulnerabilities affect Gatsby.

🚀 React 19 is here!

React 19 is now officially supported by Gatsby and all gatsby- packages maintained by the Gatsby team.

This is not a breaking change. You can safely upgrade to this release while staying on React 18.

All packages' peer dependencies on react and react-dom have been extended from ^18.0.0 to ^18.0.0 || ^19.0.0.

All existing stable Gatsby functionality is intended to now work with React 19.

PR: gatsbyjs/gatsby#39306

Upgrade Guide

[!WARNING] Community plugins may not have been updated yet to support React 19, so please check their repository for the current status. All plugins managed by the Gatsby team (in the gatsbyjs/gatsby repository) have been updated.

To upgrade to React 19, first upgrade gatsby and all your dependencies that start with gatsby- to the latest version. (Check out this guide if you need help with that.)

[!TIP] If you use npm 7 or higher you’ll want to use the --legacy-peer-deps option. For example, if you use gatsby and gatsby-plugin-postcss:

npm install --legacy-peer-deps gatsby@latest gatsby-plugin-postcss@latest

Then, follow the React 19 upgrade guide. No other changes are required.

Please note:

• Some new React 19 features may not be available yet via Gatsby.
  • Notably, the new document metadata hoisting feature is disabled in Gatsby, as it conflicts with the existing Gatsby Head API
• Gatsby Partial Hydration, an experimental feature for three years now, is known to be incompatible with React 19 at this time. If you rely on this feature, do not upgrade to React 19.

New features

Gatsby now supports React 19's new root error callbacks.

... (truncated)

Changelog

Sourced from gatsby-plugin-sharp's changelog.

5.16.0 (2026-01-26)

🧾 Release notes

Bug Fixes

• use more explicit node.js version range #39398 (c355640)

Other Changes

• Revert "chore(release): Publish next pre-minor" (3539ec8)

5.15.0 (2025-08-27)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-sharp

5.14.0 (2024-11-06)

🧾 Release notes

Bug Fixes

• update dependency fs-extra to ^11.2.0 #38727 (cb33fe5)
• update dependency async to ^3.2.5 for gatsby-plugin-sharp #38721 (a30811a)

5.13.1 (2024-01-23)

Note: Version bump only for package gatsby-plugin-sharp

5.13.0 (2023-12-18)

🧾 Release notes

Chores

• upgrade sharp to latest v0.32.6 #38374 (ca15ef3)

5.12.3 (2023-10-26)

Note: Version bump only for package gatsby-plugin-sharp

5.12.2 (2023-10-20)

Note: Version bump only for package gatsby-plugin-sharp

5.12.1 (2023-10-09)

Chores

... (truncated)

Commits

• 92d6c67 chore(release): Publish
• 3539ec8 Revert "chore(release): Publish next pre-minor"
• c355640 fix: use more explicit node.js version range (#39398)
• aea34d8 chore(release): Publish next pre-minor
• c03a920 chore(changelogs): update changelogs (#39364)
• 32f2d1e chore(release): Publish next pre-minor
• baa1b8e chore(release): Publish next
• 17baffb chore(release): Publish next pre-minor
• 5f44fcd chore(changelogs): update changelogs (#39156)
• 2c75bc5 chore(changelogs): update changelogs (#38821)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by serhalp-netlify, a new releaser for gatsby-plugin-sharp since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​lodash@​4.17.11 ⏵ 4.18.1	+1	+75	+1
	npm/​gatsby-plugin-sharp@​2.0.5 ⏵ 5.16.0		+2
	npm/​query-string@​6.14.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm hash-wasm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: yarn.lock → npm/gatsby-plugin-sharp@5.16.0 → npm/hash-wasm@4.12.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/hash-wasm@4.12.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report