meta(changelog): Update changelog for 9.23.0 #16411
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[Gitflow] Merge master into develop
It was confirmed that static pre-renders don't pick up Sentry trace meta tags — this just adds a quick test. More context: https://linear.app/getsentry/issue/JS-392/rr7-evaluate-static-pre-rendering P.S. Not a priority, but for some reason, I had to add a trailing / to fetch the correct transactions and pass the tests. I’ll look into why this is happening for transaction route names and whether this behavior is expected in a later PR. --------- Co-authored-by: Charly Gomez <charly.gomez@sentry.io>
This PR just fixes incorrect JSDoc where I missed a mix-up of incoming and outgoing requests for the `ignoreIncomingRequestBody` option while reviewing. Raised in https://github.com/getsentry/sentry-docs/pull/13698/files#r2088760944
…16351) This was tied together and could theoretically result in logs not being flushed correctly, when users opt-out of client reports. Noticed this while scanning over the browser client code :)
…s disabled (#15730) Part of #15725, this PR stops adding the `HttpInstrumentation` / `UndiciInstrumentation` if tracing is not enabled. I _think_ this should not really be breaking, as the integrations should not do anything else, if tracing is disabled 🤔 This only skips the http instrumentation without spans on node 22+, as only there our own diagnostics-channel based instrumentation can cover everything we need.
Our cloudflare SDK captures fetch exceptions in the catch block. But hono never reaches [this block](https://github.com/getsentry/sentry-javascript/blob/a874d763171289b5556973a4842f580d4bbb7ec0/packages/cloudflare/src/request.ts#L85-L90) where we send exceptions. hono processes errors with their `onError` function (or `errorHandler`) and we need to capture the exception there. This PR wraps the [`errorHandler` of hono](https://github.com/honojs/hono/blob/bb7afaccfd5b6b514da356e069f27eb5ccfc0e3b/src/hono-base.ts#L36 ). Will create an E2E test in another PR.
Adding a test to check that the build and types work (just like with cloudflare-wokers).
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Uses the established `suppressTracing` wrapper to hide Spotlight calls from OTEL too.
adds an e2e test for Angular the latest Angular 20 RC -- to be promoted to Angular 20 stable once released
…16386) This PR removes the warning for multiple browserTracingIntegrations being setup. We realised this warning was actually just a symptom of us running a bunch of the integration code in the function itself, not int `setup()`. This lead to stuff running twice when users passed in a custom integration in addition to a default one, because the logic is basically: ```js const defaultIntergations = [browserTracingIntegration()]; const usedDefinedIntegrations = [browserTracingIntegration()]; // at this point, the function was already executed twice, leading to side effects even without calling `init`! ``` Now, we move all the logic to setup/setupAfterAll, so this should be safe. This means that the integration will be deduped anyhow (I added a test to make sure this is the case), and we no longer need the warning. fixes #16369
…init()` (#16354) Similar to #16353, this changes how default options for BrowserClient are handled. Instead of building this in `init`, we now do (some) of it in BrowserClient. Additionally, this also adjusts what we do if we detect a browser extension: Instead of skipping the setup, we now just disable the client. This streamlines this a bit and also ensures that we actually always return a `Client` from init. It also fixes the type for `BrowserOption` to actually allow to configure `cdnBaseUrl`, which was actually only set for the ClientOptions, oops. The reason for this is to streamline the `init` code, making it easier to extend/adjust it. Right now, there is a lot going on in different places there. By moving as much as we can (and makes sense) to `BrowserClient` this becomes a bit easier. While playing with different ways to handle the browser extension stuff, I ended up landing on just disabling the SDK in this scenario.
….34.0 (#16393) Bumps [@opentelemetry/semantic-conventions](https://github.com/open-telemetry/opentelemetry-js) from 1.32.0 to 1.34.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/open-telemetry/opentelemetry-js/releases"><code>@opentelemetry/semantic-conventions</code>'s releases</a>.</em></p> <blockquote> <h2>semconv/v1.34.0</h2> <h2>1.34.0</h2> <h3>:rocket: Features</h3> <ul> <li>feat: update semantic conventions to v1.34.0 <a href="https://redirect.github.com/open-telemetry/opentelemetry-js/pull/5703">#5703</a> <a href="https://github.com/trentm"><code>@trentm</code></a> <ul> <li>Semantic Conventions v1.34.0: <a href="https://github.com/open-telemetry/semantic-conventions/blob/main/CHANGELOG.md#v1340">changelog</a> | <a href="https://opentelemetry.io/docs/specs/semconv/">latest docs</a></li> <li><code>@opentelemetry/semantic-conventions</code> (stable) changes: <em>none</em></li> <li><code>@opentelemetry/semantic-conventions/incubating</code> (unstable) changes: <em>12 added exports</em></li> </ul> </li> </ul> <h4>Unstable changes in v1.34.0</h4> <!-- raw HTML omitted --> <pre lang="js"><code>ATTR_AWS_BEDROCK_GUARDRAIL_ID // aws.bedrock.guardrail.id ATTR_AWS_BEDROCK_KNOWLEDGE_BASE_ID // aws.bedrock.knowledge_base.id ATTR_AWS_KINESIS_STREAM_NAME // aws.kinesis.stream_name ATTR_AWS_LAMBDA_RESOURCE_MAPPING_ID // aws.lambda.resource_mapping.id ATTR_AWS_SECRETSMANAGER_SECRET_ARN // aws.secretsmanager.secret.arn ATTR_AWS_SNS_TOPIC_ARN // aws.sns.topic.arn ATTR_AWS_SQS_QUEUE_URL // aws.sqs.queue.url ATTR_AWS_STEP_FUNCTIONS_ACTIVITY_ARN // aws.step_functions.activity.arn ATTR_AWS_STEP_FUNCTIONS_STATE_MACHINE_ARN // aws.step_functions.state_machine.arn <p>ATTR_FEATURE_FLAG_RESULT_VALUE // feature_flag.result.value</p> <p>ATTR_GEN_AI_CONVERSATION_ID // gen_ai.conversation.id<br /> ATTR_GEN_AI_DATA_SOURCE_ID // gen_ai.data_source.id<br /> </code></pre></p> <!-- raw HTML omitted --> <h2>semconv/v1.33.1</h2> <h2>1.33.1</h2> <h3>:boom: Breaking Changes</h3> <ul> <li>fix: Remove the subset of <code>DB_SYSTEM_NAME_VALUE_*</code> exports that are unstable from the <code>@opentelemetry/semantic-conventions</code> entry point. <a href="https://redirect.github.com/open-telemetry/opentelemetry-js/pull/5690">#5690</a> <ul> <li>Version 1.33.0 erroneously included all <code>DB_SYSTEM_NAME_VALUE_*</code> constants in the stable entry point. Some of those enum values are not yet stable. They have been moved back to the unstable <code>@opentelemetry/semantic-conventions/incubating</code> entry point. See the PR description for a full list.</li> </ul> </li> </ul> <h2>semconv/v1.33.0</h2> <h2>1.33.0</h2> <h3>:rocket: Features</h3> <ul> <li>feat: update semantic conventions to v1.33.0 <a href="https://redirect.github.com/open-telemetry/opentelemetry-js/pull/5654">#5654</a> <a href="https://github.com/trentm"><code>@trentm</code></a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/open-telemetry/opentelemetry-js/commit/a2e0f2c6acc1a03bc1e03cc5d59c17398c31818f"><code>a2e0f2c</code></a> chore: prepare next release (<a href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/5705">#5705</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-js/commit/019cb2c149e298f8c08291775429f2ee1827e259"><code>019cb2c</code></a> feat(semantic-conventions): update semantic conventions to v1.34.0 (<a href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/5703">#5703</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-js/commit/7a9b04904c0645c382b7f6c97afa10b653a65251"><code>7a9b049</code></a> chore: enable tsconfig isolatedModules (<a href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/5697">#5697</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-js/commit/6d0d33b3dfbc503cf28dc2db42570447b06c0303"><code>6d0d33b</code></a> chore: prepare next release (<a href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/5700">#5700</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-js/commit/280cd5012b937e5aaeeb5f2b86f51dde460ba840"><code>280cd50</code></a> test(instrumentation-fetch): pin msw dep to avoid breakage in msw@2.8 (<a href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/5702">#5702</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-js/commit/1c8ec3b291f7df63d08506f41f5d076e9a9cdcac"><code>1c8ec3b</code></a> fix(semantic-conventions): Remove the subset of <code>DB_SYSTEM_NAME_VALUE_*</code> expo...</li> <li><a href="https://github.com/open-telemetry/opentelemetry-js/commit/85f1bcc256c5a4ef7788f0e3cbbdf67a3d86edd3"><code>85f1bcc</code></a> chore(opentelemetry-instrumentation-http): Fix link to docs (<a href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/5699">#5699</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-js/commit/f0ba942c04cc671f0bede72f8c7f4cc73b88315b"><code>f0ba942</code></a> chore(deps): update dependency <code>@babel/core</code> to v7.27.1 (<a href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/5698">#5698</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-js/commit/af9c024c04c8ca0c9fa35242191f7271a5d99785"><code>af9c024</code></a> chore(deps): update all patch versions (<a href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/5694">#5694</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-js/commit/9dbd1e446be0ecc7c22b00051c5cfb2612d9b0f2"><code>9dbd1e4</code></a> chore: prepare next release (<a href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/5696">#5696</a>)</li> <li>Additional commits viewable in <a href="https://github.com/open-telemetry/opentelemetry-js/compare/semconv/v1.32.0...semconv/v1.34.0">compare view</a></li> </ul> </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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
I renamed `defaultCaptureSerializedLog` to `_INTERNAL_captureSerializedLog` and exported it so it can be accessed from other SDKs. I will use this in the Electron SDK in the root main process to add logs passed by IPC from other processes to the queue.
…InfoFromScope` works (#16385) Also ensure that `withScope(scope, callback)` maintains the active span from the passed in scope. Fixes #16361 The problem here was that we used the `_getSpanForScope` method in core for this, but this only actually works for the core implementation, not the node one 😬 So I rewrote this to use more general utilities, which should work isomorphically. While doing this, I noticed an actual bug in the `withScope` implementation in otel, where we did not actually keep the active span correctly.
Allows specific resource spans to be ignored by passing an array of strings to ignoreResourceSpans. Example values include, resource.css, resource.script. Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
When running with `spotlight: true` I got a warning about not being in development mode when `NODE_ENV` was not set. This typically indicates dev mode so added a check for that.
Bumps [@sentry/cli](https://github.com/getsentry/sentry-cli) from 2.43.0 to 2.45.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-cli/releases"><code>@sentry/cli</code>'s releases</a>.</em></p> <blockquote> <h2>2.45.0</h2> <h3>New feature</h3> <ul> <li>feat(sourcemaps): Multi-project sourcemaps upload (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2497">#2497</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a> <ul> <li>Sourcemaps can now be uploaded to multiple projects at once by passing each project to the <code>sentry-cli sourcemaps upload</code> command, like so: <pre lang="sh"><code>sentry-cli sourcemaps upload -p project1 -p project2 /path/to/sourcemaps </code></pre> </li> <li>Note that users on old versions of self-hosted Sentry may need to upgrade their self-hosted server to a newer version to take advantage of multi-project uploads.</li> </ul> </li> </ul> <h3>Various fixes & improvements</h3> <ul> <li>ref: Rename <code>fixup_js_file_end</code> (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2475">#2475</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> <li>ref: Use slice instead of vec for assemble artifact request (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2498">#2498</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> <li>ref: Separate <code>LegacyUploadContext</code> for legacy uploads (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2494">#2494</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> <li>feat: Remove organization and project info log (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2490">#2490</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> </ul> <h2>2.44.0</h2> <h3>Various fixes & improvements</h3> <ul> <li>feat(sourcemaps): Support injecting indexed sourcemaps (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2470">#2470</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> <li>test(sourcemaps): Assert injection outputs (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2483">#2483</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> </ul> <h2>2.43.1</h2> <h3>Various fixes & improvements</h3> <ul> <li>build: Bump <code>tokio</code> to <code>1.44.2</code> (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2474">#2474</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> <li>chore: Fix nightly clippy lints (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2469">#2469</a>) by <a href="https://github.com/loewenheim"><code>@loewenheim</code></a></li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-cli/blob/master/CHANGELOG.md"><code>@sentry/cli</code>'s changelog</a>.</em></p> <blockquote> <h2>2.45.0</h2> <h3>New feature</h3> <ul> <li>feat(sourcemaps): Multi-project sourcemaps upload (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2497">#2497</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a> <ul> <li>Sourcemaps can now be uploaded to multiple projects at once by passing each project to the <code>sentry-cli sourcemaps upload</code> command, like so: <pre lang="sh"><code>sentry-cli sourcemaps upload -p project1 -p project2 /path/to/sourcemaps </code></pre> </li> <li>Note that users on old versions of self-hosted Sentry may need to upgrade their self-hosted server to a newer version to take advantage of multi-project uploads.</li> </ul> </li> </ul> <h3>Various fixes & improvements</h3> <ul> <li>ref: Rename <code>fixup_js_file_end</code> (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2475">#2475</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> <li>ref: Use slice instead of vec for assemble artifact request (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2498">#2498</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> <li>ref: Separate <code>LegacyUploadContext</code> for legacy uploads (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2494">#2494</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> <li>feat: Remove organization and project info log (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2490">#2490</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> </ul> <h2>2.44.0</h2> <h3>Various fixes & improvements</h3> <ul> <li>feat(sourcemaps): Support injecting indexed sourcemaps (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2470">#2470</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> <li>test(sourcemaps): Assert injection outputs (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2483">#2483</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> </ul> <h2>2.43.1</h2> <h3>Various fixes & improvements</h3> <ul> <li>build: Bump <code>tokio</code> to <code>1.44.2</code> (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2474">#2474</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a></li> <li>chore: Fix nightly clippy lints (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2469">#2469</a>) by <a href="https://github.com/loewenheim"><code>@loewenheim</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-cli/commit/bed438e9c66f6df95e02d707c9c18ef1407f58ff"><code>bed438e</code></a> meta: Update CHANGELOG.md</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/783922560dc06887f965dca3695837b2d6ef95c7"><code>7839225</code></a> release: 2.45.0</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/47e426d94284ccc28412ae966ad1848ac6426bcd"><code>47e426d</code></a> ref: Rename <code>fixup_js_file_end</code> (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2475">#2475</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/f5ea48c24810b57d307455e262fc1580c30627c3"><code>f5ea48c</code></a> feat(sourcemaps): Multi-project sourcemaps upload (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2497">#2497</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/f540dc1c8a1e9d89d8043d97a69c5a2263c370db"><code>f540dc1</code></a> ref: Use slice instead of vec for assemble artifact request</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/8a63fec22c64ae2830fe3da0d640c2e2109dd465"><code>8a63fec</code></a> ref: Separate <code>LegacyUploadContext</code> for legacy uploads</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/b241c4a434323c0853e735768c6278d515bbe25d"><code>b241c4a</code></a> feat: Remove organization and project info log (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2490">#2490</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/046ab9de581247076d9e65cc8ea023fe35d62d08"><code>046ab9d</code></a> chore: update issue templates (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2493">#2493</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/4a0270fdf416ac31681abb4d48b9629fcf1d92d9"><code>4a0270f</code></a> build(deps): bump actions/create-github-app-token from 2.0.2 to 2.0.6 (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2485">#2485</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/1571be7371a54408f9082f66fbf099ff0ca40a76"><code>1571be7</code></a> build(deps): bump github/codeql-action from 3.28.16 to 3.28.17</li> <li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-cli/compare/2.43.0...2.45.0">compare view</a></li> </ul> </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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@sentry/webpack-plugin](https://github.com/getsentry/sentry-javascript-bundler-plugins) from 3.3.1 to 3.5.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/releases"><code>@sentry/webpack-plugin</code>'s releases</a>.</em></p> <blockquote> <h2>3.5.0</h2> <ul> <li>feat(core): Add hook to customize source map file resolution (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/732">#732</a>)</li> <li>fix(core): Avoid console output and telemetry init when plugins are disabled (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/741">#741</a>)</li> </ul> <p>Work in this release was contributed by <a href="https://github.com/thecodewarrior"><code>@thecodewarrior</code></a>. Thank you for your contribution!</p> <h2>3.4.0</h2> <ul> <li>fix: Replace existing debug ID comments (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/730">#730</a>)</li> <li>feat: Expose bundler plugin primitives via <code>createSentryBuildPluginManager</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/714">#714</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/main/CHANGELOG.md"><code>@sentry/webpack-plugin</code>'s changelog</a>.</em></p> <blockquote> <h2>3.5.0</h2> <ul> <li>feat(core): Add hook to customize source map file resolution (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/732">#732</a>)</li> <li>fix(core): Avoid console output and telemetry init when plugins are disabled (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/741">#741</a>)</li> </ul> <p>Work in this release was contributed by <a href="https://github.com/thecodewarrior"><code>@thecodewarrior</code></a>. Thank you for your contribution!</p> <h2>3.4.0</h2> <ul> <li>fix: Replace existing debug ID comments (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/730">#730</a>)</li> <li>feat: Expose bundler plugin primitives via <code>createSentryBuildPluginManager</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/714">#714</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/20e59da8b237b8f43fc2cde8488ec492015bf178"><code>20e59da</code></a> release: 3.5.0</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/bab95d92e97049b9436c8ddf39b8e77034f56d13"><code>bab95d9</code></a> meta: Add Changelog entry for 3.5.0 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/743">#743</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/4dccccaa98b92ae0af76d1abfba46912dce0d648"><code>4dcccca</code></a> chore(deps-dev): bump rollup from 2.75.7 to 2.79.2 in /packages/webpack-plugi...</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/7130a86549f240e5c3b4f884a40775efb4133ce4"><code>7130a86</code></a> fix(core): Avoid console output and telemetry init when plugins are disabled ...</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/3ba65eb7332db1fd3451ca54c38020cd571c9b30"><code>3ba65eb</code></a> chore: Add contributor attribution to changelog (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/738">#738</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/b33725e6ecd1d9990cf650fb1dac5d2da76a8c0d"><code>b33725e</code></a> feat(core): Add hook to customize source map file resolution (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/732">#732</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/7b097fc08a19c6cc1cf2dfa5d6753f08c3faed58"><code>7b097fc</code></a> Merge branch 'release/3.4.0'</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/0e15c2582bced4a151287d41103d61df3d2443fc"><code>0e15c25</code></a> release: 3.4.0</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/30c15dfd0e5c423504e9718940d6ae258ddc5bbb"><code>30c15df</code></a> meta: Update changelog for 3.4.0 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/733">#733</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/7bc20a771c8bbb321be745c790b2eca9120cc6b0"><code>7bc20a7</code></a> fix: Replace existing debug ID comments (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/730">#730</a>)</li> <li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/compare/3.3.1...3.5.0">compare view</a></li> </ul> </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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation) from 6.7.0 to 6.8.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/prisma/prisma/releases"><code>@prisma/instrumentation</code>'s releases</a>.</em></p> <blockquote> <h2>6.8.2</h2> <p>Today, we are issuing the 6.8.2 patch release. It fully resolves an issue with the <code>prisma init</code> and <code>prisma dev</code> commands for some Windows users who were still facing problems after the previous incomplete fix in version 6.8.1.</p> <p>Fixes:</p> <ul> <li><a href="https://redirect.github.com/prisma/prisma/issues/27195">prisma/prisma#27195</a></li> </ul> <h2>6.8.1</h2> <p>Today, we are issuing the 6.8.1 patch release. It fixes an issue with the <code>prisma init</code> and <code>prisma dev</code> commands on Windows.</p> <p>Fixes</p> <ul> <li><a href="https://redirect.github.com/prisma/prisma/issues/27192">prisma/prisma#27192</a></li> </ul> <h2>6.8.0</h2> <p>Today, we are excited to share the <code>6.8.0</code> stable release 🎉 </p> <p>🌟 <strong>Help us spread the word about Prisma by starring the repo ☝️ or <a href="https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v6.8.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.8.0">posting on X</a> about the release.</strong></p> <h2>Highlights</h2> <h3>Local development with Prisma Postgres via <code>prisma dev</code> (Early Access)</h3> <p>In this release, we're releasing a way to develop against Prisma Postgres <em>locally</em> — no Docker required!</p> <p>To get started, run the new <code>prisma dev</code> command:</p> <pre lang="bash"><code>npx prisma dev # starts a local Prisma Postgres server </code></pre> <p>This command spins up a local Prisma Postgres instance and prints the connection URL that you'll need to set as the <code>url</code> of your <code>datasource</code> block to point to a local Prisma Postgres instance. It looks similar to this:</p> <pre lang="prisma"><code>datasource db { provider = "postgresql" url = "prisma+postgres://localhost:51213/?api_key=ey..." } </code></pre> <p>You can then run migrations and execute queries against this local Prisma Postgres instance as with any remote one. Note that you need to keep the <code>prisma dev</code> process running in order to interact with the local Prisma Postgres instance.</p> <p>📚 Learn more in the <a href="https://www.prisma.io/docs/postgres/database/local-development">docs</a>.</p> <h3>Native Deno support in <code>prisma-client</code> generator (Preview)</h3> <p>In this release, we're removing the <code>deno</code> Preview feature from the <code>prisma-client-js</code> generator. If you want to use Prisma ORM with Deno, you can now do so with the new <a href="https://www.prisma.io/docs/orm/prisma-schema/overview/generators#prisma-client-early-access"><code>prisma-client</code></a> generator:</p> <pre lang="prisma"><code>generator client { provider = "prisma-client" output = "../src/generated/prisma" </tr></table> </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/prisma/prisma/commits/6.8.2/packages/instrumentation">compare view</a></li> </ul> </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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Added ability to detect and import config files from the **active** nuxt layer with strategy of the **most latest** layer taking precedence. Included fallback behavior for good measure. Rest of the config should be merged as it already is by c12 and defu. Don't think this PR covers the git:repo based layers but those are generally not full supported as well in Nuxt 3 ecosystem. Added basic tests Resolves [#14345](#14345) --------- Co-authored-by: Ivan Pesic <pesic.ivan@feg.eu>
This was forgotten to re-export. We actually document this, but have not exported it, oops.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #16372 Co-authored-by: s1gr1d <32902192+s1gr1d@users.noreply.github.com>
The Sentry Nuxt SDK emits the Sentry config file during the Rollup build. Users add this file to their application which includes an import from `@sentry/nuxt` and the init function. This file is then added as an `.mjs` file in the build output. However, when building the application, this `.mjs` file included a bunch of OpenTelemetry imports and not only the init code as every dependency from `@sentry/nuxt` was traced back and bundled into the build output. By adding `@sentry/nuxt` as external, the `.mjs` file really only contains the content like in the `.ts` file. **Could** fix #15204 --------- Co-authored-by: Andrei Borza <andrei.borza@sentry.io>
size-limit report 📦
|
AbhiPrasad
reviewed
May 28, 2025
CHANGELOG.md
Outdated
|
|
||
| - feat: Export `isEnabled` from all SDKs ([#16405](https://github.com/getsentry/sentry-javascript/pull/16405)) | ||
| - feat(browser): Disable client when browser extension is detected in `init()` ([#16354](https://github.com/getsentry/sentry-javascript/pull/16354)) | ||
| - feat(browser): option to ignore certain resource types ([#16389](https://github.com/getsentry/sentry-javascript/pull/16389)) |
There was a problem hiding this comment.
I'd add a note about this as an important change, and share a code snippet as well.
Sentry.browserTracingIntegration({
ignoreResourceSpans: ['resource.script'],
}),
andreiborza
force-pushed
the
prepare-release/9.23.0
branch
from
2a3da17 to
5eca427
Compare
Lms24
approved these changes
May 28, 2025
AbhiPrasad
approved these changes
May 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.