build(deps): bump @sentry/browser from 10.27.0 to 10.33.0

[dependabot]

Bumps @sentry/browser from 10.27.0 to 10.33.0.

Release notes

Sourced from @​sentry/browser's releases.

10.33.0

Important Changes

• feat(core): Apply scope attributes to metrics (#18738)

  You can now set attributes on the SDK's scopes which will be applied to all metrics as long as the respective scopes are active. For the time being, only string, number and boolean attribute values are supported.

  Sentry.getGlobalScope().setAttributes({ is_admin: true, auth_provider: 'google' });
  Sentry.withScope(scope => {
  scope.setAttribute('step', 'authentication');
  // scope attributes is_admin, auth_provider and step are added
  Sentry.metrics.count('clicks', 1, { attributes: { activeSince: 100 } });
  Sentry.metrics.gauge('timeSinceRefresh', 4, { unit: 'hour' });
  });
  // scope attributes is_admin and auth_provider are added
  Sentry.metrics.count('response_time', 283.33, { unit: 'millisecond' });

• feat(tracing): Add Vercel AI SDK v6 support (#18741)

  The Sentry SDK now supports the Vercel AI SDK v6. Tracing and error monitoring will work automatically with the new version.

• feat(wasm): Add applicationKey option for third-party error filtering (#18762)

  Adds support for applying an application key to WASM stack frames that can be then used in the thirdPartyErrorFilterIntegration for detection of first-party code.

  Usage:

  Sentry.init({
    integrations: [
      // Integration order matters: wasmIntegration needs to be before thirdPartyErrorFilterIntegration
      wasmIntegration({ applicationKey: 'your-custom-application-key' }), ←───┐
      thirdPartyErrorFilterIntegration({                                      │
        behaviour: 'drop-error-if-exclusively-contains-third-party-frames',   ├─ matching keys
        filterKeys: ['your-custom-application-key'] ←─────────────────────────┘
      }),
    ],
  });

Other Changes

• feat(cloudflare): Support propagateTraceparent (#18569)
• feat(core): Add ignoreSentryInternalFrames option to thirdPartyErrorFilterIntegration (#18632)
• feat(core): Add gen_ai.conversation.id attribute to OpenAI and LangGr… (#18703)

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

10.33.0

Important Changes

• feat(core): Apply scope attributes to metrics (#18738)

  You can now set attributes on the SDK's scopes which will be applied to all metrics as long as the respective scopes are active. For the time being, only string, number and boolean attribute values are supported.

  Sentry.getGlobalScope().setAttributes({ is_admin: true, auth_provider: 'google' });
  Sentry.withScope(scope => {
  scope.setAttribute('step', 'authentication');
  // scope attributes is_admin, auth_provider and step are added
  Sentry.metrics.count('clicks', 1, { attributes: { activeSince: 100 } });
  Sentry.metrics.gauge('timeSinceRefresh', 4, { unit: 'hour' });
  });
  // scope attributes is_admin and auth_provider are added
  Sentry.metrics.count('response_time', 283.33, { unit: 'millisecond' });

• feat(tracing): Add Vercel AI SDK v6 support (#18741)

  The Sentry SDK now supports the Vercel AI SDK v6. Tracing and error monitoring will work automatically with the new version.

• feat(wasm): Add applicationKey option for third-party error filtering (#18762)

  Adds support for applying an application key to WASM stack frames that can be then used in the thirdPartyErrorFilterIntegration for detection of first-party code.

  Usage:

  Sentry.init({
    integrations: [
      // Integration order matters: wasmIntegration needs to be before thirdPartyErrorFilterIntegration
      wasmIntegration({ applicationKey: 'your-custom-application-key' }), ←───┐
      thirdPartyErrorFilterIntegration({                                      │
        behaviour: 'drop-error-if-exclusively-contains-third-party-frames',   ├─ matching keys
        filterKeys: ['your-custom-application-key'] ←─────────────────────────┘
      }),
    ],
  });

Other Changes

• feat(cloudflare): Support propagateTraceparent (#18569)
• feat(core): Add ignoreSentryInternalFrames option to thirdPartyErrorFilterIntegration (#18632)

... (truncated)

Commits

• fb9dd1e release: 10.33.0
• b7fe9bf Merge pull request #18770 from getsentry/prepare-release/10.33.0
• 1630389 meta(changelog): Update changelog for 10.33.0
• 3ff89c6 test(node-integration): Remove hardcoded SDK version assertions (#18775)
• 03546d2 test(node-core): Fix wrong import in node core IPv6 integration test (#18773)
• 6f723e0 fix(test): Remove hard-coded SDK version assertion (#18771)
• ac45e57 feat(nextjs): Print Turbopack note for deprecated webpack options (#18769)
• cc93c68 feat(cloudflare): Support propagateTraceparent (#18569)
• 46225eb feat(wasm): Add applicationKey option for third-party error filtering (#18762)
• fd42f3b fix(next): Wrap all Random APIs with a safe runner (#18700)
• Additional commits viewable in compare view

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

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• Support for Capacitor V8 by lucas-zimerman in #1071

Build / dependencies / internal 🔧

• (deps) Bump @sentry/browser from 10.27.0 to 10.33.0 by dependabot[bot] in #1078

---

_{🤖 This preview updates automatically when you update the PR.}

[sentry]

Bug: The update to @sentry/browser without also updating @sentry/core creates a dependency version conflict, as they are part of a monorepo and expect to be aligned.
_{Severity: CRITICAL}

🔍 Detailed Analysis

This change updates @sentry/browser to version 10.33.0 while leaving @sentry/core at 10.27.0. Since @sentry/[email protected] has a dependency on @sentry/[email protected], this creates a version conflict. When this package is consumed, package managers may hoist the wrong version or install duplicates of @sentry/core. This can lead to runtime errors, such as "undefined is not a function", because the code from @sentry/browser might call functions from @sentry/core that have changed or do not exist in the older version. This type of version misalignment is a known issue for Sentry's monorepo packages.

💡 Suggested Fix

Update all related @sentry/ packages (@sentry/core, @sentry/types, etc.) to the same version as @sentry/browser (10.33.0). Packages from the Sentry monorepo should be kept in sync to avoid version conflicts.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L61-L63

Potential issue: This change updates `@sentry/browser` to version `10.33.0` while
leaving `@sentry/core` at `10.27.0`. Since `@sentry/[email protected]` has a dependency on
`@sentry/[email protected]`, this creates a version conflict. When this package is consumed,
package managers may hoist the wrong version or install duplicates of `@sentry/core`.
This can lead to runtime errors, such as "undefined is not a function", because the code
from `@sentry/browser` might call functions from `@sentry/core` that have changed or do
not exist in the older version. This type of version misalignment is a known issue for
Sentry's monorepo packages.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 8495538}