Sourced from pnpm's releases.

pnpm 10.17

Minor Changes

• The minimumReleaseAgeExclude setting now supports patterns. For instance:

  minimumReleaseAge: 1440
  minimumReleaseAgeExclude:
    - "@eslint/*"
  

  Related PR: #9984.

Patch Changes

• Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #9978.
• When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #9979.

Platinum Sponsors

Gold Sponsors

... (truncated)

Sourced from pnpm's changelog.

10.17.0

Minor Changes

• The minimumReleaseAgeExclude setting now supports patterns. For instance:

  minimumReleaseAge: 1440
  minimumReleaseAgeExclude:
    - "@eslint/*"
  

  Related PR: #9984.

Patch Changes

• Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #9978.
• When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #9979.

• 1a1a272 chore(release): 10.17.0
• See full diff in compare view

• See full diff in compare view

• 8e2a592 Patch to 2.8.5 because browser or feature data changed
• 79b38d3 Browser or feature data changed
• 87e05ba Fixes for older versions of node (#101)
• 387bee3 Update issue templates
• See full diff in compare view

• See full diff in compare view

Sourced from esbuild's releases.

v0.25.10

• Fix a panic in a minification edge case (#4287)

  This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value undefined in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):

  function identity(x) { return x }
  identity({ y: identity(123) })
  

• Fix @supports nested inside pseudo-element (#4265)

  When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as ::placeholder for correctness. The CSS nesting specification says the following:

  The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

  However, it seems like this behavior is different for nested at-rules such as @supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:

  /* Original code */
  ::placeholder {
    color: red;
    body & { color: green }
    @supports (color: blue) { color: blue }
  }
  /* Old output (with --supported:nesting=false) */
  
  ::placeholder {
  
  color: red;
  
  }
  
  body :is() {
  
  color: green;
  
  }
  
  @​supports (color: blue) {
  
  {
  
  color: blue;
  
  }
  
  }
  /* New output (with --supported:nesting=false) */
  
  ::placeholder {
  
  color: red;
  
  }
  
  body :is() {
  
  color: green;
  
  }
  
  @​supports (color: blue) {
  
  ::placeholder {
  
  color: blue;
  
  }
  
  

... (truncated)

Sourced from esbuild's changelog.

0.25.10

• Fix a panic in a minification edge case (#4287)

  This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value undefined in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):

  function identity(x) { return x }
  identity({ y: identity(123) })
  

• Fix @supports nested inside pseudo-element (#4265)

  When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as ::placeholder for correctness. The CSS nesting specification says the following:

  The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

  However, it seems like this behavior is different for nested at-rules such as @supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:

  /* Original code */
  ::placeholder {
    color: red;
    body & { color: green }
    @supports (color: blue) { color: blue }
  }
  /* Old output (with --supported:nesting=false) */
  
  ::placeholder {
  
  color: red;
  
  }
  
  body :is() {
  
  color: green;
  
  }
  
  @​supports (color: blue) {
  
  {
  
  color: blue;
  
  }
  
  }
  /* New output (with --supported:nesting=false) */
  
  ::placeholder {
  
  color: red;
  
  }
  
  body :is() {
  
  color: green;
  
  }
  
  @​supports (color: blue) {
  
  ::placeholder {
  
  color: blue;
  
  

... (truncated)

• d6b668f publish 0.25.10 to npm
• 5088c19 refactor: use strings.Builder (#4290)
• 755da31 run make update-compat-table
• a1d9c86 fix #4287: marked the wrong issue as fixed
• 73a0b2a fix #4286: minifier panic due to identity function
• 134dadf fix #4265: @supports nested inside ::pseudo
• See full diff in compare view

Sourced from sharp's releases.

v0.34.4

• Upgrade to libvips v8.17.2 for upstream bug fixes.

• Ensure TIFF subifd and OpenSlide level input options are respected (regression in 0.34.3).

• Ensure autoOrient occurs before non-90 angle rotation. #4425

• Ensure autoOrient removes existing metadata after shrink-on-load. #4431

• TypeScript: Ensure KernelEnum includes linear. #4441 @​BayanBennett

• Ensure unlimited flag is passed upstream when reading TIFF images. #4446

• Support Electron memory cage when reading XMP metadata (regression in 0.34.3). #4451

• Add sharp-libvips rpath for yarn v5 support. #4452 @​arcanis

v0.34.4-rc.4

• Upgrade to libvips v8.17.2 for upstream bug fixes.

• Ensure TIFF subifd and OpenSlide level input options are respected (regression in 0.34.3).

• Ensure autoOrient occurs before non-90 angle rotation. #4425

• Ensure autoOrient removes existing metadata after shrink-on-load. #4431

• TypeScript: Ensure KernelEnum includes linear. #4441 @​BayanBennett

• Ensure unlimited flag is passed upstream when reading TIFF images. #4446

• Support Electron memory cage when reading XMP metadata (regression in 0.34.3). #4451

• Add sharp-libvips rpath for yarn v5 support. #4452 @​arcanis

... (truncated)

• ee43783 Release v0.34.4
• 5299011 CI/Docs: Deno v2 support
• 4710092 Prerelease v0.34.4-rc.4
• ed1ac43 CI: Upgrade packaging test dependencies
• dfcbcee Upgrade sharp-libvips to v1.2.3
• 35d3f56 Ensure TIFF subifd and OpenSlide level are respected
• 9f4bace Prerelease v0.34.4-rc.3
• b507831 CI: Remove dry-run flag
• 905f698 Prerelease v0.34.4-rc.2
• b0154ed Upgrade sharp-libvips to v1.2.2
• Additional commits viewable in compare view

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for sharp since your current version.

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions