Sourced from @​napi-rs/simple-git's releases.

v0.1.22

What's Changed

• Replace unmaintained goto-bus-stop/setup-zig with mlugg/setup-zig action by @​Copilot in Brooooooklyn/simple-git#96
• chore(deps): update actions/download-artifact action to v5 by @​renovate[bot] in Brooooooklyn/simple-git#97
• chore: clippy fix and npm trusted publisher by @​Brooooooklyn in Brooooooklyn/simple-git#99

New Contributors

• @​Copilot made their first contribution in Brooooooklyn/simple-git#96

Full Changelog: https://github.com/Brooooooklyn/simple-git/compare/v0.1.21...v0.1.22

• 7d01607 0.1.22
• 5792944 chore: fix preversion script
• 6cbeb6e chore: clippy fix and npm trusted publisher (#99)
• a1dfc9b chore(deps): update actions/download-artifact action to v5 (#97)
• 919cd79 ci: replace unmaintained goto-bus-stop/setup-zig with mlugg/setup-zig action ...
• See full diff in compare view

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​napi-rs/simple-git since your current version.

Sourced from preact's releases.

10.27.1

Performance

• Avoid re-inserting children during bailout (#4890, thanks @​vasylenkoval)

Types

• add missing React.Key (#4864, thanks @​shyguy1412)
• make React.SVGAttributes generic (#4863, thanks @​shyguy1412)

Fixes

• Add .render property referencing original render function (#4870, thanks @​upupming)
• Add .type property referencing original component (#4869, thanks @​upupming)

Maintenance

• Fix benchmarks for v10.x (#4891, thanks @​rschristian)
• Correct contributing docs (#4861, thanks @​JoviDeCroock)

• 02b52e6 10.27.1 (#4892)
• 28a56ca ci: Fix benchmarks workflow for v10.x (#4891)
• d92da32 Port #4888 to v10 (#4890)
• 89ad340 Merge pull request #4870 from upupming/v10.x-forward-ref-render-field
• d698fd2 Merge pull request #4869 from upupming/v10.x-memo-type-field
• 5eada63 fix(compat): add .render property referencing original render function
• e25d0b9 feat: add .type property referencing original component
• cf39a4b fix(types) preact/compat missing React.Key (#4864)
• 058573c fix(types) make React.SVGAttributes generic (#4863)
• 2a48070 Accoutn for v10.x branch (#4861)
• See full diff in compare view

• See full diff in compare view

Sourced from esbuild's releases.

v0.25.9

• Better support building projects that use Yarn on Windows (#3131, #3663)

  With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

  1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
  2. Some developers put their projects on the D: drive
  3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
  4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
  5. I didn't have access to a Windows machine for testing this edge case

  Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

• Preserve parentheses around function expressions (#4252)

  The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

  Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

  // Original code
  const fn0 = () => 0
  const fn1 = (() => 1)
  console.log(fn0, function() { return fn1() }())
  // Old output
  
  const fn0 = () => 0;
  
  const fn1 = () => 1;
  
  console.log(fn0, function() {
  
  return fn1();
  
  }());
  // New output
  
  const fn0 = () => 0;
  
  const fn1 = (() => 1);
  
  console.log(fn0, (function() {
  
  return fn1();
  
  })());
  
  

  Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

• Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

  This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

Sourced from esbuild's changelog.

0.25.9

• Better support building projects that use Yarn on Windows (#3131, #3663)

  With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

  1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
  2. Some developers put their projects on the D: drive
  3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
  4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
  5. I didn't have access to a Windows machine for testing this edge case

  Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

• Preserve parentheses around function expressions (#4252)

  The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

  Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

  // Original code
  const fn0 = () => 0
  const fn1 = (() => 1)
  console.log(fn0, function() { return fn1() }())
  // Old output
  
  const fn0 = () => 0;
  
  const fn1 = () => 1;
  
  console.log(fn0, function() {
  
  return fn1();
  
  }());
  // New output
  
  const fn0 = () => 0;
  
  const fn1 = (() => 1);
  
  console.log(fn0, (function() {
  
  return fn1();
  
  })());
  
  

  Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

• Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

  This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

• 195e05c publish 0.25.9 to npm
• 3dac33f fix #3131, fix #3663: yarnpnp + windows + D drive
• 0f2c5c8 mock fs now supports multiple volumes on windows
• 100a51e split out yarnpnp snapshot tests
• 13aace3 remove C: assumption from windows snapshot tests
• f1f413f fix #4252: preserve parentheses around functions
• 1bc8091 fix #4257, close #4258: go 1.23.10 => 1.23.12
• bc52135 move the go compiler version to go.version
• a0af5d1 makefile: use ESBUILD_VERSION consistently
• See full diff in compare view

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