dependabot[bot] opened a new pull request, #332: URL: https://github.com/apache/arrow-js/pull/332
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.25.10 to 0.27.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases";>esbuild's releases</a>.</em></p> <blockquote> <h2>v0.27.0</h2> <p><strong>This release deliberately contains backwards-incompatible changes.</strong> To avoid automatically picking up releases like this, you should either be pinning the exact version of <code>esbuild</code> in your <code>package.json</code> file (recommended) or be using a version range syntax that only accepts patch upgrades such as <code>^0.26.0</code> or <code>~0.26.0</code>. See npm's documentation about <a href="https://docs.npmjs.com/cli/v6/using-npm/semver/";>semver</a> for more information.</p> <ul> <li> <p>Use <code>Uint8Array.fromBase64</code> if available (<a href="https://redirect.github.com/evanw/esbuild/issues/4286";>#4286</a>)</p> <p>With this release, esbuild's <code>binary</code> loader will now use the new <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Uint8Array/fromBase64";><code>Uint8Array.fromBase64</code></a> function unless it's unavailable in the configured target environment. If it's unavailable, esbuild's previous code for this will be used as a fallback. Note that this means you may now need to specify <code>target</code> when using this feature with Node (for example <code>--target=node22</code>) unless you're using Node v25+.</p> </li> <li> <p>Update the Go compiler from v1.23.12 to v1.25.4 (<a href="https://redirect.github.com/evanw/esbuild/issues/4208";>#4208</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4311";>#4311</a>)</p> <p>This raises the operating system requirements for running esbuild:</p> <ul> <li>Linux: now requires a kernel version of 3.2 or later</li> <li>macOS: now requires macOS 12 (Monterey) or later</li> </ul> </li> </ul> <h2>v0.26.0</h2> <ul> <li> <p>Enable trusted publishing (<a href="https://redirect.github.com/evanw/esbuild/issues/4281";>#4281</a>)</p> <p>GitHub and npm are recommending that maintainers for packages such as esbuild switch to <a href="https://docs.npmjs.com/trusted-publishers";>trusted publishing</a>. With this release, a VM on GitHub will now build and publish all of esbuild's packages to npm instead of me. In theory.</p> <p>Unfortunately there isn't really a way to test that this works other than to do it live. So this release is that live test. Hopefully this release is uneventful and is exactly the same as the previous one (well, except for the green provenance attestation checkmark on npm that happens with trusted publishing).</p> </li> </ul> <h2>v0.25.12</h2> <ul> <li> <p>Fix a minification regression with CSS media queries (<a href="https://redirect.github.com/evanw/esbuild/issues/4315";>#4315</a>)</p> <p>The previous release introduced support for parsing media queries which unintentionally introduced a regression with the removal of duplicate media rules during minification. Specifically the grammar for <code>@media <media-type> and <media-condition-without-or> { ... }</code> was missing an equality check for the <code><media-condition-without-or></code> part, so rules with different suffix clauses in this position would incorrectly compare equal and be deduplicated. This release fixes the regression.</p> </li> <li> <p>Update the list of known JavaScript globals (<a href="https://redirect.github.com/evanw/esbuild/issues/4310";>#4310</a>)</p> <p>This release updates esbuild's internal list of known JavaScript globals. These are globals that are known to not have side-effects when the property is accessed. For example, accessing the global <code>Array</code> property is considered to be side-effect free but accessing the global <code>scrollY</code> property can trigger a layout, which is a side-effect. This is used by esbuild's tree-shaking to safely remove unused code that is known to be side-effect free. This update adds the following global properties:</p> <p>From <a href="https://tc39.es/ecma262/2017/";>ES2017</a>:</p> <ul> <li><code>Atomics</code></li> <li><code>SharedArrayBuffer</code></li> </ul> <p>From <a href="https://tc39.es/ecma262/2020/";>ES2020</a>:</p> <ul> <li><code>BigInt64Array</code></li> <li><code>BigUint64Array</code></li> </ul> <p>From <a href="https://tc39.es/ecma262/2021/";>ES2021</a>:</p> <ul> <li><code>FinalizationRegistry</code></li> <li><code>WeakRef</code></li> </ul> <p>From <a href="https://tc39.es/ecma262/2025/";>ES2025</a>:</p> <ul> <li><code>Float16Array</code></li> <li><code>Iterator</code></li> </ul> <p>Note that this does not indicate that constructing any of these objects is side-effect free, just that accessing the identifier is side-effect free. For example, this now allows esbuild to tree-shake classes that extend from <code>Iterator</code>:</p> <pre lang="js"><code>// This can now be tree-shaken by esbuild: </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md";>esbuild's changelog</a>.</em></p> <blockquote> <h2>0.27.0</h2> <p><strong>This release deliberately contains backwards-incompatible changes.</strong> To avoid automatically picking up releases like this, you should either be pinning the exact version of <code>esbuild</code> in your <code>package.json</code> file (recommended) or be using a version range syntax that only accepts patch upgrades such as <code>^0.26.0</code> or <code>~0.26.0</code>. See npm's documentation about <a href="https://docs.npmjs.com/cli/v6/using-npm/semver/";>semver</a> for more information.</p> <ul> <li> <p>Use <code>Uint8Array.fromBase64</code> if available (<a href="https://redirect.github.com/evanw/esbuild/issues/4286";>#4286</a>)</p> <p>With this release, esbuild's <code>binary</code> loader will now use the new <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Uint8Array/fromBase64";><code>Uint8Array.fromBase64</code></a> function unless it's unavailable in the configured target environment. If it's unavailable, esbuild's previous code for this will be used as a fallback. Note that this means you may now need to specify <code>target</code> when using this feature with Node (for example <code>--target=node22</code>) unless you're using Node v25+.</p> </li> <li> <p>Update the Go compiler from v1.23.12 to v1.25.4 (<a href="https://redirect.github.com/evanw/esbuild/issues/4208";>#4208</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4311";>#4311</a>)</p> <p>This raises the operating system requirements for running esbuild:</p> <ul> <li>Linux: now requires a kernel version of 3.2 or later</li> <li>macOS: now requires macOS 12 (Monterey) or later</li> </ul> </li> </ul> <h2>0.26.0</h2> <ul> <li> <p>Enable trusted publishing (<a href="https://redirect.github.com/evanw/esbuild/issues/4281";>#4281</a>)</p> <p>GitHub and npm are recommending that maintainers for packages such as esbuild switch to <a href="https://docs.npmjs.com/trusted-publishers";>trusted publishing</a>. With this release, a VM on GitHub will now build and publish all of esbuild's packages to npm instead of me. In theory.</p> <p>Unfortunately there isn't really a way to test that this works other than to do it live. So this release is that live test. Hopefully this release is uneventful and is exactly the same as the previous one (well, except for the green provenance attestation checkmark on npm that happens with trusted publishing).</p> </li> </ul> <h2>0.25.12</h2> <ul> <li> <p>Fix a minification regression with CSS media queries (<a href="https://redirect.github.com/evanw/esbuild/issues/4315";>#4315</a>)</p> <p>The previous release introduced support for parsing media queries which unintentionally introduced a regression with the removal of duplicate media rules during minification. Specifically the grammar for <code>@media <media-type> and <media-condition-without-or> { ... }</code> was missing an equality check for the <code><media-condition-without-or></code> part, so rules with different suffix clauses in this position would incorrectly compare equal and be deduplicated. This release fixes the regression.</p> </li> <li> <p>Update the list of known JavaScript globals (<a href="https://redirect.github.com/evanw/esbuild/issues/4310";>#4310</a>)</p> <p>This release updates esbuild's internal list of known JavaScript globals. These are globals that are known to not have side-effects when the property is accessed. For example, accessing the global <code>Array</code> property is considered to be side-effect free but accessing the global <code>scrollY</code> property can trigger a layout, which is a side-effect. This is used by esbuild's tree-shaking to safely remove unused code that is known to be side-effect free. This update adds the following global properties:</p> <p>From <a href="https://tc39.es/ecma262/2017/";>ES2017</a>:</p> <ul> <li><code>Atomics</code></li> <li><code>SharedArrayBuffer</code></li> </ul> <p>From <a href="https://tc39.es/ecma262/2020/";>ES2020</a>:</p> <ul> <li><code>BigInt64Array</code></li> <li><code>BigUint64Array</code></li> </ul> <p>From <a href="https://tc39.es/ecma262/2021/";>ES2021</a>:</p> <ul> <li><code>FinalizationRegistry</code></li> <li><code>WeakRef</code></li> </ul> <p>From <a href="https://tc39.es/ecma262/2025/";>ES2025</a>:</p> <ul> <li><code>Float16Array</code></li> <li><code>Iterator</code></li> </ul> <p>Note that this does not indicate that constructing any of these objects is side-effect free, just that accessing the identifier is side-effect free. For example, this now allows esbuild to tree-shake classes that extend from <code>Iterator</code>:</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/2b91699b74da07c2cd2361a5e63c1882575e3bf0";><code>2b91699</code></a> publish 0.27.0 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/22b425c12f59964383df27362294b5f8c034bab3";><code>22b425c</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4286";>#4286</a>: use <code>Uint8Array.fromBase64</code> if present (<a href="https://redirect.github.com/evanw/esbuild/issues/4295";>#4295</a>)</li> <li><a href="https://github.com/evanw/esbuild/commit/6d187ef4c9277939c1639ef8c036c07ff62dd33f";><code>6d187ef</code></a> update go 1.25.3 => 1.25.4</li> <li><a href="https://github.com/evanw/esbuild/commit/9d0d4e71a23dce02d18cf91552304333c1b44cd9";><code>9d0d4e7</code></a> update go 1.23.12 => 1.25.3 (<a href="https://redirect.github.com/evanw/esbuild/issues/4318";>#4318</a>)</li> <li><a href="https://github.com/evanw/esbuild/commit/b6979d89ed4b2aed1ab58d206e65c8bd92ac7c60";><code>b6979d8</code></a> use a patched go compiler for release builds</li> <li><a href="https://github.com/evanw/esbuild/commit/893d2b9661a62575041fa371351c422f887cc43d";><code>893d2b9</code></a> delete temporary <code>release.yml</code> workflow</li> <li><a href="https://github.com/evanw/esbuild/commit/cee391852c39146334894795e658e7a9c7bc4cd8";><code>cee3918</code></a> add a temporary <code>release.yml</code> workflow</li> <li><a href="https://github.com/evanw/esbuild/commit/f5bb1d6ed8c86eea24cda1664ab8812d823daeca";><code>f5bb1d6</code></a> fix <code>publish.yml</code></li> <li><a href="https://github.com/evanw/esbuild/commit/17ff82bebfaf78e97457cb504525584e603bf9f4";><code>17ff82b</code></a> publish 0.26.0 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/f87181fbf3eb78b6b00cf7b3529d0f6f20cd763c";><code>f87181f</code></a> enable trusted publishing (<a href="https://redirect.github.com/evanw/esbuild/issues/4319";>#4319</a>)</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.25.10...v0.27.0";>compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by [GitHub Actions](<a href="https://www.npmjs.com/~GitHub";>https://www.npmjs.com/~GitHub</a> Actions), a new releaser for esbuild since your current version.</p> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
