Update sharp → 0.33.1 (unknown) #1061
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ sharp (^0.30.4 → ^0.33.1) · Repo
Commits
See the full diff on Github. The new version differs by 28 commits:
Release v0.33.1Prerelease v0.33.1-rc.3CI: Split yarn pnp package tests into separate jobsDocs: refresh index and homepage linkPrerelease v0.33.1-rc.2CI: Pin Node.js 18 to avoid npm 10 on 32-bit WindowsPrerelease v0.33.1-rc.1Improve resilience of installation checkCI: Upgrade to latest FreeBSD, improve test resilienceDocs: changelog and credit for #3897Ensure VIPS_NOVECTOR env var is respected (#3897)Emit warning for invalid ICC profile #3895Tests: attempt to reduce chance of race conditionDocs: improve cross-platform help messagingAdd help when possibly using an unsupported libcDocs: update liborc references to highwayCI: Ensure Yarn pnp linker uses ESMPrerelease v0.33.1-rc.0Add help text for Node.js snap failuresTests: tighten yarn locator test for multi-platformImprove help text displayed on failure of requireTests: improve yarn locator coverageCI: Add package test for Yarn Plug'n'PlayAllow yarn locator hash calc to fail e.g. WindowsAdd support for Yarn Plug'n'Play filesystem layout #3888Docs: clarify yarn v1 vs yarn v3+ installation #3871Docs: make use of optional dependencies even clearerDocs: highlight that optional deps must be allowedDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands