Bump phin, gatsby-plugin-sharp, gatsby-remark-images and gatsby-transformer-sharp

[dependabot[bot]]

Removes phin. It's no longer used after updating ancestor dependencies phin, gatsby-plugin-sharp, gatsby-remark-images and gatsby-transformer-sharp. These dependencies need to be updated together.

Removes phin

Updates gatsby-plugin-sharp from 2.14.4 to 5.13.1

Release notes

Sourced from gatsby-plugin-sharp's releases.

v5.13.0

Welcome to [email protected] release (December 2023 #1)

Key highlight of this release:

• Custom Image and File CDN URL generators

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

v5.12.0

Welcome to [email protected] release (August 2023 #1)

Key highlight of this release:

• Adapters

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

v5.11.0

Welcome to [email protected] release (June 2023 #1)

Key highlights of this release:

• RFC: Adapters
• gatsby-source-wordpress: Support for multiple instances

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.10.0

Welcome to [email protected] release (May 2023 #1)

This release focused on bug fixes and perf improvements. Check out notable bugfixes and improvements.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.9.0

Welcome to [email protected] release (April 2023 #1)

... (truncated)

Changelog

Sourced from gatsby-plugin-sharp's changelog.

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

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

5.12.0 (2023-08-24)

🧾 Release notes

Bug Fixes

• update dependency semver to ^7.5.3 #38296 (11e64e2)

5.11.0 (2023-06-15)

🧾 Release notes

Chores

• update semver #38171 (208cdef)

5.10.0 (2023-05-16)

🧾 Release notes

Bug Fixes

• update dependency sharp to ^0.32.1 #38024 (d7cccfe)
• update dependency semver to ^7.5.0 #38023 (2564f6b)

... (truncated)

Commits

• b24134d chore(release): Publish
• 18ffcfa chore(release): Publish
• 26871b8 chore(release): Publish next
• 9a26700 chore(changelogs): update changelogs (#38667)
• 7ba63eb chore(changelogs): update changelogs (#38658)
• d90d747 chore(changelogs): update changelogs (#38642)
• ca15ef3 chore(deps): upgrade sharp to latest v0.32.6 (#38374)
• db248ab chore(changelogs): update changelogs (#38526)
• e6e2fb4 chore(release): Publish next pre-minor
• 1ebae56 chore(release): Publish next
• Additional commits viewable in compare view

Updates gatsby-remark-images from 3.11.1 to 7.13.1

Release notes

Sourced from gatsby-remark-images's releases.

v5.13.0

Welcome to [email protected] release (December 2023 #1)

Key highlight of this release:

• Custom Image and File CDN URL generators

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

v5.12.0

Welcome to [email protected] release (August 2023 #1)

Key highlight of this release:

• Adapters

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

v5.11.0

Welcome to [email protected] release (June 2023 #1)

Key highlights of this release:

• RFC: Adapters
• gatsby-source-wordpress: Support for multiple instances

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.10.0

Welcome to [email protected] release (May 2023 #1)

This release focused on bug fixes and perf improvements. Check out notable bugfixes and improvements.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.9.0

Welcome to [email protected] release (April 2023 #1)

... (truncated)

Changelog

Sourced from gatsby-remark-images's changelog.

7.13.1 (2024-01-23)

Note: Version bump only for package gatsby-remark-images

7.13.0 (2023-12-18)

🧾 Release notes

Note: Version bump only for package gatsby-remark-images

7.12.3 (2023-10-26)

Note: Version bump only for package gatsby-remark-images

7.12.2 (2023-10-20)

Note: Version bump only for package gatsby-remark-images

7.12.1 (2023-10-09)

Note: Version bump only for package gatsby-remark-images

7.12.0 (2023-08-24)

🧾 Release notes

Note: Version bump only for package gatsby-remark-images

7.11.0 (2023-06-15)

🧾 Release notes

Note: Version bump only for package gatsby-remark-images

7.10.0 (2023-05-16)

🧾 Release notes

Note: Version bump only for package gatsby-remark-images

7.9.0 (2023-04-18)

🧾 Release notes

Note: Version bump only for package gatsby-remark-images

7.8.0 (2023-03-21)

🧾 Release notes

... (truncated)

Commits

• b24134d chore(release): Publish
• 18ffcfa chore(release): Publish
• 26871b8 chore(release): Publish next
• 9a26700 chore(changelogs): update changelogs (#38667)
• 7ba63eb chore(changelogs): update changelogs (#38658)
• d90d747 chore(changelogs): update changelogs (#38642)
• db248ab chore(changelogs): update changelogs (#38526)
• e6e2fb4 chore(release): Publish next pre-minor
• 1ebae56 chore(release): Publish next
• fd4d702 chore(changelogs): update changelogs (#38248)
• Additional commits viewable in compare view

Updates gatsby-transformer-sharp from 2.12.1 to 5.13.1

Release notes

Sourced from gatsby-transformer-sharp's releases.

v5.13.0

Welcome to [email protected] release (December 2023 #1)

Key highlight of this release:

• Custom Image and File CDN URL generators

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

v5.12.0

Welcome to [email protected] release (August 2023 #1)

Key highlight of this release:

• Adapters

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

v5.11.0

Welcome to [email protected] release (June 2023 #1)

Key highlights of this release:

• RFC: Adapters
• gatsby-source-wordpress: Support for multiple instances

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.10.0

Welcome to [email protected] release (May 2023 #1)

This release focused on bug fixes and perf improvements. Check out notable bugfixes and improvements.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.9.0

Welcome to [email protected] release (April 2023 #1)

... (truncated)

Changelog

Sourced from gatsby-transformer-sharp's changelog.

5.13.1 (2024-01-23)

Note: Version bump only for package gatsby-transformer-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-transformer-sharp

5.12.2 (2023-10-20)

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

5.12.1 (2023-10-09)

Chores

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

5.12.0 (2023-08-24)

🧾 Release notes

Bug Fixes

• update dependency semver to ^7.5.3 #38296 (11e64e2)

5.11.0 (2023-06-15)

🧾 Release notes

Chores

• update semver #38171 (208cdef)

5.10.0 (2023-05-16)

🧾 Release notes

Bug Fixes

• update dependency sharp to ^0.32.1 #38024 (d7cccfe)
• update dependency semver to ^7.5.0 #38023 (2564f6b)

... (truncated)

Commits

• b24134d chore(release): Publish
• 18ffcfa chore(release): Publish
• 26871b8 chore(release): Publish next
• 9a26700 chore(changelogs): update changelogs (#38667)
• 7ba63eb chore(changelogs): update changelogs (#38658)
• d90d747 chore(changelogs): update changelogs (#38642)
• ca15ef3 chore(deps): upgrade sharp to latest v0.32.6 (#38374)
• db248ab chore(changelogs): update changelogs (#38526)
• e6e2fb4 chore(release): Publish next pre-minor
• 1ebae56 chore(release): Publish next
• Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	filesystem	0	150 kB	ryanzim

View full report↗︎

[socket-security[bot]]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/[email protected]	Install script: install Source: node install	orphan: npm/[email protected]
Known Malware	npm/[email protected]	Note: This package downloads prebuilt artifacts from a domain which has been compromised. Your system may be infected if you installed this package prior to April 27, 2023	orphan: npm/[email protected]

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

What is known malware?

This package is malware. We have asked the package registry to remove it.

It is strongly recommended that malware is removed from your codebase.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]