publish: getsentry/[email protected]

[getsentry-release]

Requested by: @lforst

Merge target: master

Quick links:

• View changes
• View check runs

Assign the accepted label to this issue to approve the release.
Leave a comment containing #retract under this issue to retract the release (original issuer only).

Targets

• npm[@sentry/types]
• npm[@sentry/utils]
• npm[@sentry/core]
• npm[@sentry-internal/browser-utils]
• npm[@sentry-internal/replay]
• npm[@sentry/opentelemetry]
• npm[@sentry-internal/feedback]
• npm[@sentry-internal/replay-canvas]
• npm[@sentry/browser]
• npm[@sentry/node]
• npm[@sentry/profiling-node]
• npm[@sentry/angular]
• npm[@sentry/ember]
• npm[@sentry/react]
• npm[@sentry/solid]
• npm[@sentry/svelte]
• npm[@sentry/vue]
• npm[@sentry/wasm]
• npm[@sentry/vercel-edge]
• npm[@sentry/cloudflare]
• npm[@sentry/deno]
• commit-on-git-repository[getsentry/deno]
• npm[@sentry/aws-serverless]
• npm[@sentry/google-cloud-serverless]
• npm[@sentry/bun]
• npm[@sentry/nestjs]
• npm[@sentry/nextjs]
• npm[@sentry/nuxt]
• npm[@sentry/remix]
• npm[@sentry/solidstart]
• npm[@sentry/sveltekit]
• npm[@sentry/gatsby]
• npm[@sentry/astro]
• npm[@sentry-internal/typescript]
• npm[@sentry-internal/eslint-plugin-sdk]
• npm[@sentry-internal/eslint-config-sdk]
• aws-lambda-layer
• gcs[browser-cdn-bundles]
• github
• registry

Targets marked with a checkbox have already been executed. Administrators can manually tick a checkbox to force craft to skip it.

[mydea]

Looking at one thing in the release where I am not 100% sure we want to ship this, verifiying...

[mydea]

After checking in with @s1gr1d we decided to revert getsentry/sentry-javascript#14047 and revisit this in a more tree-shakeable way. @lforst can you retract the release?

[lforst]

#retract

[github-actions]

Release request retracted by @lforst.
You may also want to remove your release branch.