Bump the dev-dependencies group across 1 directory with 5 updates

[dependabot]

Updates the requirements on @sentry/browser, caniuse-lite, @sentry/cli, @wordpress/eslint-plugin and esbuild to permit the latest version.
Updates @sentry/browser to 10.24.0

Release notes

Sourced from @​sentry/browser's releases.

10.24.0

Important Changes

• feat(metrics): Add top level option enableMetrics and beforeSendMetric (#18088)

  This PR moves enableMetrics and beforeSendMetric out of the _experiments options. The metrics feature will now be enabled by default (none of our integrations will auto-emit metrics as of now), but you can disable sending metrics via enableMetrics: false. Metric options within _experiments got deprecated but will still work as of now, they will be removed with the next major version of our SDKs.

Other Changes

• feat(aws): Add SENTRY_LAYER_EXTENSION to configure using the lambda layer extension via env variables (#18101)
• feat(core): Include all exception object keys instead of truncating (#18044)
• feat(metrics)!: Update types (#17907)
• feat(replay): ignore background-image when blockAllMedia is enabled (#18019)
• fix(nextjs): Delete css map files (#18131)
• fix(nextjs): Stop accessing sync props in template (#18113)

• chore: X handle update (#18117)
• chore(eslint): Add eslint-plugin-regexp rule (dev-packages) (#18063)
• test(next): fix flakey tests (#18100)
• test(node-core): Proof that withMonitor doesn't create a new trace (#18057)

Bundle size 📦

Path	Size
@​sentry/browser	24.02 KB
@​sentry/browser - with treeshaking flags	22.54 KB
@​sentry/browser (incl. Tracing)	40.26 KB
@​sentry/browser (incl. Tracing, Profiling)	44.43 KB
@​sentry/browser (incl. Tracing, Replay)	77.83 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	67.75 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	82.42 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	94.3 KB
@​sentry/browser (incl. Feedback)	40.3 KB
@​sentry/browser (incl. sendFeedback)	28.58 KB
@​sentry/browser (incl. FeedbackAsync)	33.39 KB
@​sentry/react	25.68 KB
@​sentry/react (incl. Tracing)	42.2 KB
@​sentry/vue	28.39 KB
@​sentry/vue (incl. Tracing)	41.99 KB
@​sentry/svelte	24.03 KB
CDN Bundle	26.26 KB
CDN Bundle (incl. Tracing)	40.79 KB
CDN Bundle (incl. Tracing, Replay)	76.46 KB

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

10.24.0

Important Changes

• feat(metrics): Add top level option enableMetrics and beforeSendMetric (#18088)

  This PR moves enableMetrics and beforeSendMetric out of the _experiments options. The metrics feature will now be enabled by default (none of our integrations will auto-emit metrics as of now), but you can disable sending metrics via enableMetrics: false. Metric options within _experiments got deprecated but will still work as of now, they will be removed with the next major version of our SDKs.

Other Changes

• feat(aws): Add SENTRY_LAYER_EXTENSION to configure using the lambda layer extension via env variables (#18101)
• feat(core): Include all exception object keys instead of truncating (#18044)
• feat(metrics)!: Update types (#17907)
• feat(replay): ignore background-image when blockAllMedia is enabled (#18019)
• fix(nextjs): Delete css map files (#18131)
• fix(nextjs): Stop accessing sync props in template (#18113)

• chore: X handle update (#18117)
• chore(eslint): Add eslint-plugin-regexp rule (dev-packages) (#18063)
• test(next): fix flakey tests (#18100)
• test(node-core): Proof that withMonitor doesn't create a new trace (#18057)

10.23.0

• feat(core): Send user-agent header with envelope requests in server SDKs (#17929)
• feat(browser): Limit transport buffer size (#18046)
• feat(core): Remove default value of maxValueLength: 250 (#18043)
• feat(react-router): Align options with shared build time options type (#18014)
• fix(browser-utils): cache element names for INP (#18052)
• fix(browser): Capture unhandled rejection errors for web worker integration (#18054)
• fix(cloudflare): Ensure types for cloudflare handlers (#18064)
• fix(nextjs): Update proxy template wrapping (#18086)
• fix(nuxt): Added top-level fallback exports (#18083)
• fix(nuxt): check for H3 error cause before re-capturing (#18035)
• fix(replay): Linked errors not resetting session id (#17854)
• fix(tracemetrics): Bump metrics buffer to 1k (#18039)
• fix(vue): Make options parameter optional on attachErrorHandler (#18072)
• ref(core): Set span status internal_error instead of unknown_error (#17909)

• fix(tests): un-override nitro dep version for nuxt-3 test (#18056)
• fix(e2e): Add p-map override to fix React Router 7 test builds (#18068)

... (truncated)

Commits

• 907546f release: 10.24.0
• e861b4f Merge pull request #18133 from getsentry/prepare-release/10.24.0
• 0054094 meta(changelog): Update changelog for 10.24.0
• 10211f4 fix(nextjs): Delete css map files (#18131)
• d26e1a9 feat(aws): Add SENTRY_LAYER_EXTENSION to configure using the lambda layer e...
• d4a2b2b test(next): fix flakey tests (#18100)
• 27af12e fix(nextjs): Stop accessing sync props in template (#18113)
• 296e860 chore: X handle update (#18117)
• c2530dd feat(metrics): Add top level option enableMetrics and beforeSendMetric (#...
• ad870cf feat(metrics)!: Update types (#17907)
• Additional commits viewable in compare view

Updates caniuse-lite to 1.0.30001754

Commits

• a088d8c Update caniuse-db 1.0.30001754
• 9cb8427 Update caniuse-db 1.0.30001753
• 52fb80d Update caniuse-db 1.0.30001752
• See full diff in compare view

Updates @sentry/cli to 2.58.0

Release notes

Sourced from @​sentry/cli's releases.

2.58.0

New Features

• Removed experimental status from the sentry-cli build upload commands (#2899, #2905). At the time of this release, build uploads are still in closed beta on the server side, so most customers cannot use this functionality quite yet.
• Added CLI version metadata to build upload archives (#2890).

Deprecations

• Deprecated the upload-proguard subcommand's --platform flag (#2863). This flag was a no-op for some time, so we will remove it in the next major.
• Deprecated the upload-proguard subcommand's --android-manifest flag (#2891). This flag was a no-op for some time, so we will remove it in the next major.
• Deprecated the sentry-cli sourcemaps upload command's --no-dedupe flag (#2913). The flag was no longer relevant for sourcemap uploads to modern Sentry servers and was made a no-op.

Fixes

• Fixed autofilled git base metadata (--base-ref, --base-sha) when using the build upload subcommand in git repos. Previously this worked only in the context of GitHub workflows (#2897, #2898).

Performance

• Slightly sped up the sentry-cli sourcemaps upload command by eliminating an HTTP request to the Sentry server, which was not required in most cases (#2913).

Changelog

Sourced from @​sentry/cli's changelog.

2.58.0

New Features

• Removed experimental status from the sentry-cli build upload commands (#2899, #2905). At the time of this release, build uploads are still in closed beta on the server side, so most customers cannot use this functionality quite yet.
• Added CLI version metadata to build upload archives (#2890).

Deprecations

• Deprecated the upload-proguard subcommand's --platform flag (#2863). This flag was a no-op for some time, so we will remove it in the next major.
• Deprecated the upload-proguard subcommand's --android-manifest flag (#2891). This flag was a no-op for some time, so we will remove it in the next major.
• Deprecated the sentry-cli sourcemaps upload command's --no-dedupe flag (#2913). The flag was no longer relevant for sourcemap uploads to modern Sentry servers and was made a no-op.

Fixes

• Fixed autofilled git base metadata (--base-ref, --base-sha) when using the build upload subcommand in git repos. Previously this worked only in the context of GitHub workflows (#2897, #2898).

Performance

• Slightly sped up the sentry-cli sourcemaps upload command by eliminating an HTTP request to the Sentry server, which was not required in most cases (#2913).

2.57.0

New Features

• (JS API) Add projects field to SentryCliUploadSourceMapsOptions (#2856)

Deprecations

• Deprecated the upload-proguard subcommand's --app-id, --version, and --version-code flags (#2852), as we plan to remove these flags in Sentry CLI 3.x. Users should simply stop using the flags; the values specified there have never had an effect on deobfuscation, and are no longer visible in Sentry.
• Added a deprecation notice for release bundle uploads, a legacy method for uploading source maps (#2844). Release bundle uploads will be removed in Sentry CLI 3.x in favor of artifact bundles, the newer source map upload method introduced in Sentry version 23.6.2. Self-hosted users: You must upgrade to Sentry 23.6.2 or later before upgrading to Sentry CLI 3.x.

Fixes

• Fixed a bug where some log messages would not show up in CI environments or when redirecting stderr to a file (#2830). Specifically, this bug was affecting any subcommand that uses a progress bar, such as sentry-cli debug-files bundle-jvm and sentry-cli sourcemaps upload. Any stderr output during the progress bar was lost if stderr was redirected.

2.56.1

Deprecations

• Added a deprecation notice for legacy uploading methods (#2836, #2837)
  • Support for these legacy uploading methods, required to upload to self-hosted Sentry servers below version 10.0.0, will be removed in the next major release (3.x). If you observe these new deprecation notices, we recommend upgrading your self-hosted Sentry server, or pinning Sentry CLI to a compatible version (2.x).
  • You may encounter these deprecation notices when uploading debug files or sourcemaps.

Fixes & improvements

• Fixed a bug with sourcemap injection (#2764) by @​szokeasaurusrex
  • This change ensures we do not attempt to associate multiple compiled sources with the same sourcemap. As there should be at most one sourcemap for each compiled source, associating multiple compiled sources with the same sourcemap would lead to an invalid state.
• Updated some outdated dependencies (#2816, #2818, and #2819)

... (truncated)

Commits

• 8c07798 release: 2.58.0
• dffbfa6 meta(changelog): Prepare for release (#2915)
• 1b7a748 refactor(build): Simplify get_version and add test comment (#2914)
• 0a030d4 feat(build): Add CLI version metadata to build upload archives (#2890)
• ccb71af perf(sourcemaps): Elminate unnecessary HTTP call (#2913)
• 3f51037 meta(codeowners): Grant JS team co-codeownership of some files (#2911)
• ff7306e fix(preprod): Mention build upload is non-experimental in CHANGELOG
• bec709e fix(vcs): Fix local find_base_sha test
• 198d1ae Update src/utils/vcs.rs
• ad76996 fix(vcs): Make git_repo_base_ref return ref
• Additional commits viewable in compare view

Updates @wordpress/eslint-plugin to 22.20.0

Changelog

Sourced from @​wordpress/eslint-plugin's changelog.

22.20.0 (2025-10-29)

22.19.0 (2025-10-17)

22.18.0 (2025-10-01)

22.17.0 (2025-09-17)

22.16.0 (2025-09-03)

22.15.0 (2025-08-20)

22.14.0 (2025-08-07)

22.13.0 (2025-07-23)

Enhancements

• Added stricter ESLint checks for translator comments.
• Supports unnamed (%s, %d, %f), positional (%1$s, etc.) and named placeholders.
• Flags missing and extra/outdated placeholders.

22.12.0 (2025-06-25)

22.11.0 (2025-06-04)

22.10.0 (2025-05-22)

22.9.0 (2025-05-07)

22.8.0 (2025-04-11)

22.7.0 (2025-03-27)

22.6.0 (2025-03-13)

22.5.0 (2025-02-28)

22.4.0 (2025-02-12)

22.3.0 (2025-01-29)

22.2.0 (2025-01-15)

22.1.0 (2025-01-02)

22.0.0 (2024-12-11)

Breaking Changes

... (truncated)

Commits

• ceebff8 chore(release): publish
• d63dedd Update changelog files
• See full diff in compare view

Updates esbuild from 0.25.12 to 0.27.0

Release notes

Sourced from esbuild's releases.

v0.27.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.26.0 or ~0.26.0. See npm's documentation about semver for more information.

• Use Uint8Array.fromBase64 if available (#4286)

  With this release, esbuild's binary loader will now use the new Uint8Array.fromBase64 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 target when using this feature with Node (for example --target=node22) unless you're using Node v25+.

• Update the Go compiler from v1.23.12 to v1.25.4 (#4208, #4311)

  This raises the operating system requirements for running esbuild:

  • Linux: now requires a kernel version of 3.2 or later
  • macOS: now requires macOS 12 (Monterey) or later

v0.26.0

• Enable trusted publishing (#4281)

  GitHub and npm are recommending that maintainers for packages such as esbuild switch to trusted publishing. With this release, a VM on GitHub will now build and publish all of esbuild's packages to npm instead of me. In theory.

  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).

Changelog

Sourced from esbuild's changelog.

0.27.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.26.0 or ~0.26.0. See npm's documentation about semver for more information.

• Use Uint8Array.fromBase64 if available (#4286)

  With this release, esbuild's binary loader will now use the new Uint8Array.fromBase64 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 target when using this feature with Node (for example --target=node22) unless you're using Node v25+.

• Update the Go compiler from v1.23.12 to v1.25.4 (#4208, #4311)

  This raises the operating system requirements for running esbuild:

  • Linux: now requires a kernel version of 3.2 or later
  • macOS: now requires macOS 12 (Monterey) or later

0.26.0

• Enable trusted publishing (#4281)

  GitHub and npm are recommending that maintainers for packages such as esbuild switch to trusted publishing. With this release, a VM on GitHub will now build and publish all of esbuild's packages to npm instead of me. In theory.

  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).

Commits

• 2b91699 publish 0.27.0 to npm
• 22b425c fix #4286: use Uint8Array.fromBase64 if present (#4295)
• 6d187ef update go 1.25.3 => 1.25.4
• 9d0d4e7 update go 1.23.12 => 1.25.3 (#4318)
• b6979d8 use a patched go compiler for release builds
• 893d2b9 delete temporary release.yml workflow
• cee3918 add a temporary release.yml workflow
• f5bb1d6 fix publish.yml
• 17ff82b publish 0.26.0 to npm
• f87181f enable trusted publishing (#4319)
• Additional commits viewable in compare view

Maintainer changes

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

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 commands and options

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