Bump sharp from 0.31.1 to 0.32.6 #56
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
the
dependencies
|
Important Auto Review SkippedBot user detected. To trigger a single review, invoke the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit's AI:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
|
@LeoDog896 I'm not that familiar with JS/TS tooling, but I can't see that "sharp ^0.31.1" requirement anywhere in the repo after this PR. Is that coming from the package manager's requirement itself or some cache? |
|
It seems as if Parcel itself is trying to say that it needs sharp v.0.31.1 (Parcel's package manager utility tries to automatically resolve dependencies from Dependabot made this PR because of CVE-2023-4863 - since this site is built statically, it is not affected by it. |
|
Is there a way to force Parcel to use that specified version? |
|
Not yet - that version breaks compat with the sharp config, so it requires manual updating (this PR is essentially blocked by parcel-bundler/parcel#8976) |
|
@dependabot recreate |
Bumps [sharp](https://github.com/lovell/sharp) from 0.31.1 to 0.32.6. - [Release notes](https://github.com/lovell/sharp/releases) - [Changelog](https://github.com/lovell/sharp/blob/main/docs/changelog.md) - [Commits](lovell/sharp@v0.31.1...v0.32.6) --- updated-dependencies: - dependency-name: sharp dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/sharp-0.32.6
branch
from
db76f07 to
7442ce6
Compare
Bumps sharp from 0.31.1 to 0.32.6.
Changelog
Sourced from sharp's changelog.
... (truncated)
Commits
eefaa99Release v0.32.6dbce6faUpgrade to libvips v8.14.5af0fcb3Docs: changelog for #3799c6f54e5Bump devDeps846563eTypeScript: add definitions for block and unblock (#3799)9c217abEnsure withMetadata can add RGB16 profiles #3773e7381e5Alternative fix for 4340d60, uses existing StaySequential4340d60Ensure composite tile images fully decoded #37677f64d46Docs: add missing returns property to raw67e927bDocs: ensure all functions include method signature #3777You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.