meta(changelog): Update changelog for 10.2.0 #17339
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
We skipped this because some dependency issues made this break, it seems to work again.
…17299) Adjusts the `mechanism.type` field for errors caught `onerror` or `onunhandledrejection`. Aligns the naming scheme with [trace origin](https://develop.sentry.dev/sdk/telemetry/traces/trace-origin/) naming scheme. ref #17250 ref #17212
…ild LLM calls (#17281) ## Problem Currently, `gen_ai.invoke_agent` spans (representing operations like `generateText()`) contain inaccurate token usage information. Users can only see token data on individual `gen_ai.generate_text` child spans, but the tokens are not accumulated across nested spans, making it difficult to track total token consumption for complete AI operations. ## Solution Implement token accumulation for `gen_ai.invoke_agent` spans by iterating over client LLM child spans and aggregating their token usage.
…ge (#17297) Noticed this by chance, this is a redundant message (we also use this as general fallback anyhow). The two messages have been: ``` Unable to send Feedback. This is because of network issues, or because you are using an ad-blocker. Unable to send Feedback. This could be because of network issues, or because you are using an ad-blocker ``` Which are virtually identical. We can safe some bytes there IMHO.
[Gitflow] Merge master into develop
Streamlines solidstart build logs: 1. Only show messages when `debug: true` 2. Show short message when sourcemaps: false and debug: false
…edback (#17236) I noticed that our replays w/ feedbacks have gaps while the user is entering in their feedback. This is because we call `replay.flush` (not to be confused w/ the public replay integration integration which also has a flush) which only flushes the buffer and continues to buffer. What we want is to call `sendBufferedReplayOrFlush` which will convert the buffered replay into a session replay (after flushing) in order to continue recording.
Streamlines react router build logs. Those are mostly already gated behind `debug`, so smaller changes here: 1. Streamline with style from other parts of the SDK 2. Log compact message when source maps are disabled without `debug: true` 3. Add some tests for this
Don't inject tracing meta tags on cached HTML pages (SWR and pre-rendered pages). This means won't have connected traces for those pages anymore. But before, multiple pageloads were listed in one trace as they were all connected to one backend request. Closes #16045 I spent most of the time creating the tests for this PR and verifying it works - the logic is so small 😅 ### Notes for reviewing - the test setup is the same in nuxt-3-min and nuxt-4.
This adds a new `ignoreSpans` option to all SDKs which can be used as
follows:
```js
Sentry.init({
ignoreSpans: ['partial match', /regex/, { name: 'span name', op: 'http.client' }]
});
```
this will drop spans before they are sent. Eventual child spans in the
same envelope will be re-parented, if possible.
Closes #16820
---------
Co-authored-by: Lukas Stracke <[email protected]>
the TODO says this is _likely_ not needed anymore since OTel correctly wraps the handler in all cases (I never ran into any situation where it didn't). Also, when a user would use `Sentry.wrapHandler` manually, the detection mechanism checking whether the handler was already wrapped by OTel would not work anyway, since it that case OTel wraps it only *after* we did, resulting in double spans. Also also, removing this makes our lives easier for streaming, where this resulted in some issues with overlapping spans.
Bumps [@sentry/webpack-plugin](https://github.com/getsentry/sentry-javascript-bundler-plugins) from 4.0.0 to 4.0.2. <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>4.0.2</h2> <ul> <li>fix(core): Make <code>moduleMetadata</code> injection snippet ES5-compliant (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/774">#774</a>)</li> </ul> <h2>4.0.1</h2> <ul> <li>fix(core): Make plugin inject ES5-friendly code (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/770">#770</a>)</li> <li>fix(core): Use <code>renderChunk</code> for release injection for Rollup/Rolldown/Vite (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/761">#761</a>)</li> </ul> <p>Work in this release was contributed by <a href="https://github.com/grushetsky"><code>@grushetsky</code></a>. Thank you for your contribution!</p> </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>4.0.2</h2> <ul> <li>fix(core): Make <code>moduleMetadata</code> injection snippet ES5-compliant (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/774">#774</a>)</li> </ul> <h2>4.0.1</h2> <ul> <li>fix(core): Make plugin inject ES5-friendly code (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/770">#770</a>)</li> <li>fix(core): Use <code>renderChunk</code> for release injection for Rollup/Rolldown/Vite (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/761">#761</a>)</li> </ul> <p>Work in this release was contributed by <a href="https://github.com/grushetsky"><code>@grushetsky</code></a>. Thank you for your contribution!</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/46da015550ae4cf1594e13e8ec7519740b4ed0e8"><code>46da015</code></a> release: 4.0.2</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/335b03826ef88096e5ecf9cdd16a805627de3b73"><code>335b038</code></a> meta: Add Changelog entry for 4.0.2 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/776">#776</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/f2cdce6eef40366b9e0cc5e345e6e4e7bda378af"><code>f2cdce6</code></a> fix(core): Make <code>moduleMetadata</code> injection snippet ES5-compliant (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/774">#774</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/bdb1cfbdfda25d47ff935d6ca3dae39debdd61bf"><code>bdb1cfb</code></a> Merge branch 'release/4.0.1'</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/b8576501adf65ffe4f451096e61e12904d825cc5"><code>b857650</code></a> release: 4.0.1</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/0a956e7f6494889e472f0a7be428bb34b7cbe646"><code>0a956e7</code></a> meta: Update changelog for 4.0.1 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/771">#771</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/223d05496258dfed98c62e1788f999c33aa2bd7b"><code>223d054</code></a> fix: Use <code>renderChunk</code> for release injection for Rollup/Rolldown/Vite (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/761">#761</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/8237ac982d7eb79b6abec8bde0bb18f7a3d1face"><code>8237ac9</code></a> fix(core): Make plugin inject ES5-friendly code (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/770">#770</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/8f059c2928d1338f1313fa9864a27718874e77ab"><code>8f059c2</code></a> Merge branch 'release/4.0.0'</li> <li>See full diff in <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/compare/4.0.0...4.0.2">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] <[email protected]> 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.12.0 to 6.13.0. <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.13.0</h2> <p>Today, we are excited to share the <code>6.13.0</code> stable release 🎉</p> <p><strong>🌟 Star this repo for notifications about new releases, bug fixes & features — or <a href="https://pris.ly/x">follow us on X</a>!</strong></p> <h2>Highlights</h2> <p>In this ORM release, we’re moving the Prisma Config file and the multi-schema feature into <a href="https://www.prisma.io/docs/orm/more/releases#generally-available-ga">General Availability</a>. This means these features now are fully production-ready and we’re looking forward to seeing what you are going to build with them!</p> <p>Additionally, support for SQL views is getting an important update to further stabilize its API.</p> <h3>Configuring Prisma via Prisma Config is now Generally Available</h3> <p>The <a href="https://www.prisma.io/docs/orm/reference/prisma-config-reference"><code>prisma.config.ts</code></a> file is Prisma ORM’s native way to provide configuration options for your project. It currently lets you specify:</p> <ul> <li>the locations for various Prisma-related assets, such as your: <ul> <li>Prisma schema file</li> <li>migrations</li> <li>SQL view definitions</li> <li>TypedSQL queries</li> </ul> </li> <li>a <code>seed</code> command to populate your database based on some executable script</li> <li>externally managed tables (see below)</li> <li>the driver adapters to be used by the Prisma CLI when interacting with your database</li> </ul> <p>Here’s an example Prisma Config file that specified custom locations for various project assets in and a seed script inside a <code>db</code> directory:</p> <pre lang="tsx"><code>import path from "node:path"; import { defineConfig } from "prisma/config"; <p>export default defineConfig({<br /> schema: path.join("db", "schema.prisma"),<br /> migrations: {<br /> path: path.join("db", "migrations"),<br /> seed: "tsx db/seed.ts"<br /> }<br /> });<br /> </code></pre></p> <p>Note that you’ll also see warning now if you defined a <code>prisma.seed</code> command in <code>package.json</code>.</p> <p>We’re excited to move the <a href="https://www.prisma.io/docs/orm/reference/prisma-config-reference"><code>prisma.config.ts</code></a> file into General Availability. If you used it before in your projects, you can now drop <code>earlyAccess</code> from its options:</p> <pre lang="diff"><code>import { defineConfig } from "prisma/config"; <p>export default defineConfig({</p> <ul> <li>earlyAccess: true,<br /> });<br /> </code></pre></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/prisma/prisma/commits/6.13.0/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] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@sentry/rollup-plugin](https://github.com/getsentry/sentry-javascript-bundler-plugins) from 4.0.0 to 4.0.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/releases"><code>@sentry/rollup-plugin</code>'s releases</a>.</em></p> <blockquote> <h2>4.0.2</h2> <ul> <li>fix(core): Make <code>moduleMetadata</code> injection snippet ES5-compliant (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/774">#774</a>)</li> </ul> <h2>4.0.1</h2> <ul> <li>fix(core): Make plugin inject ES5-friendly code (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/770">#770</a>)</li> <li>fix(core): Use <code>renderChunk</code> for release injection for Rollup/Rolldown/Vite (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/761">#761</a>)</li> </ul> <p>Work in this release was contributed by <a href="https://github.com/grushetsky"><code>@grushetsky</code></a>. Thank you for your contribution!</p> </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/rollup-plugin</code>'s changelog</a>.</em></p> <blockquote> <h2>4.0.2</h2> <ul> <li>fix(core): Make <code>moduleMetadata</code> injection snippet ES5-compliant (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/774">#774</a>)</li> </ul> <h2>4.0.1</h2> <ul> <li>fix(core): Make plugin inject ES5-friendly code (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/770">#770</a>)</li> <li>fix(core): Use <code>renderChunk</code> for release injection for Rollup/Rolldown/Vite (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/pull/761">#761</a>)</li> </ul> <p>Work in this release was contributed by <a href="https://github.com/grushetsky"><code>@grushetsky</code></a>. Thank you for your contribution!</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/46da015550ae4cf1594e13e8ec7519740b4ed0e8"><code>46da015</code></a> release: 4.0.2</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/335b03826ef88096e5ecf9cdd16a805627de3b73"><code>335b038</code></a> meta: Add Changelog entry for 4.0.2 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/776">#776</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/f2cdce6eef40366b9e0cc5e345e6e4e7bda378af"><code>f2cdce6</code></a> fix(core): Make <code>moduleMetadata</code> injection snippet ES5-compliant (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/774">#774</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/bdb1cfbdfda25d47ff935d6ca3dae39debdd61bf"><code>bdb1cfb</code></a> Merge branch 'release/4.0.1'</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/b8576501adf65ffe4f451096e61e12904d825cc5"><code>b857650</code></a> release: 4.0.1</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/0a956e7f6494889e472f0a7be428bb34b7cbe646"><code>0a956e7</code></a> meta: Update changelog for 4.0.1 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/771">#771</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/223d05496258dfed98c62e1788f999c33aa2bd7b"><code>223d054</code></a> fix: Use <code>renderChunk</code> for release injection for Rollup/Rolldown/Vite (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/761">#761</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/8237ac982d7eb79b6abec8bde0bb18f7a3d1face"><code>8237ac9</code></a> fix(core): Make plugin inject ES5-friendly code (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/770">#770</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/8f059c2928d1338f1313fa9864a27718874e77ab"><code>8f059c2</code></a> Merge branch 'release/4.0.0'</li> <li>See full diff in <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/compare/4.0.0...4.0.2">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] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Adds an important change entry for #16820 for the next release
This streamlines astro build logs in two ways: 1. Guard all logs (except the deprecation warning) behind `debug: true` 2. Use the astro logger instead of `console.log` everywhere. This automatically prepends the message with `@sentry/astro`, so no need for our own prefix there - see https://docs.astro.build/en/reference/integrations-reference/#astrointegrationlogger 3. If `sourceMaps: false` is explicitly set by a user, we always show a short warning, and a longer warning with more context when `debug: true`
This updates nuxt build logs a bit: 1. Make sure everything is gated behind `debug: true` 2. Show short message when sourceMaps: false without `debug: true` 3. Adjust messages to align with other SDKs a bit more. 4. Avoid `consoleSandbox` which we do not need there
…ced` decorator (#17318) Every automatically started span from our instrumentation should include an origin attribute. Also added the `sentry.op` attribute for completeness
Bumps [@sentry/cli](https://github.com/getsentry/sentry-cli) from 2.50.0 to 2.50.2. <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.50.2</h2> <p>This change removes the <code>mobile-app upload</code> experimental feature which was introduced in 2.50.1.</p> <h2>2.50.1</h2> <h3>Various fixes & improvements</h3> <ul> <li>build(deps): bump form-data from 3.0.1 to 3.0.4 (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2638">#2638</a>) by <a href="https://github.com/dependabot"><code>@dependabot</code></a></li> </ul> <h3>New experimental feature</h3> <p>This release introduces the new experimental <code>mobile-app upload</code> subcommand. This command is experimental, and therefore subject to changes, including breaking changes and/or removal, in any release. The command might not work as expected.</p> </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.50.2</h2> <p>This change removes the <code>mobile-app upload</code> experimental feature which was introduced in 2.50.1.</p> <h2>2.50.1</h2> <h3>Various fixes & improvements</h3> <ul> <li>build(deps): bump form-data from 3.0.1 to 3.0.4 (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2638">#2638</a>) by <a href="https://github.com/dependabot"><code>@dependabot</code></a></li> </ul> <h3>New experimental feature</h3> <p>This release introduces the new experimental <code>mobile-app upload</code> subcommand. This command is experimental, and therefore subject to changes, including breaking changes and/or removal, in any release. The command might not work as expected.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-cli/commit/c9274e989e41da4202e68dc6a4c40262a6c7391a"><code>c9274e9</code></a> meta: Update CHANGELOG.md</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/23ca6040b9aef19be63412f72bb30dfd64622523"><code>23ca604</code></a> release: 2.50.2</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/eccd48c3836350166e19a458fcd2b286d58d5af9"><code>eccd48c</code></a> feat(mobile-app): Reintroduce mobile-app feature gating (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2643">#2643</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/61e8637d934386966f7b773ddf780dae1f2f1a0c"><code>61e8637</code></a> ci: Enable <code>uninlined-format-args</code> Clippy lint (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2634">#2634</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/db5e5e46413671e98ed5d28a9a6e6fa7f1d1b954"><code>db5e5e4</code></a> ci(test): Replace <code>--all</code> with <code>--workspace</code> (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2640">#2640</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/cc3caf6fbd61b72bc5720572833bf2476388124f"><code>cc3caf6</code></a> build: Delete <code>Makefile</code> (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2641">#2641</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/e998b33fd4031d1a37dc88b18130c9d27c27ee85"><code>e998b33</code></a> build(deps): bump github/codeql-action from 3.29.2 to 3.29.3 (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2637">#2637</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/727629890a3043abf37d3231ccd6b1d082af0bb2"><code>7276298</code></a> build(deps): bump form-data from 3.0.1 to 3.0.4 (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2638">#2638</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/952feeb58f7ef928904bb590ca3fcea1b5317b42"><code>952feeb</code></a> feat(mobile-app): Remove unstable-mobile-app feature gating (<a href="https://redirect.github.com/getsentry/sentry-cli/issues/2601">#2601</a>)</li> <li><a href="https://github.com/getsentry/sentry-cli/commit/fcc6506bdc96e6ad6caad2a4631383e38981672f"><code>fcc6506</code></a> feat(mobile-app): Add extra experimental logging to the mobile-app subcommand...</li> <li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-cli/compare/2.50.0...2.50.2">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] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…17320) Both of: - import OpenAI from `openai` - import { OpenAI } from`openai` Should point to the instrumented wrapper function.
Cursor's bugbot PR review feature accepts [custom rules](https://docs.cursor.com/en/bugbot#rules). Let's use this to enhance Cursor's reviewing capabilities with SDK-specific conventions. This PR adds a couple of them, paired with some more general important concerns. As a general rule of thumb: Let's add things that are hard to lint against but should still be flagged (like span origin or exception mechanisms). If this causes cursor to spam us with crap, we can always make things more or less specific of course. But I think this is worth a try.
This PR: - Creates a new individual page for `8.x` changelog entry so that we reduce the size of the main `CHANGELOG.md` - Updates the `v7` and `v8` changelogs to be updated to their latest releases - Updates the main changelog entry to add v9 releases that were not tracked before
Merged #17327 before I could include these changes
This PR copies what we did for Node (#17218) but for the Chromium stack parser.
…17338) Adds support for OpenAI manual instrumentation in `@sentry/cloudflare` and `@sentry/vercel-edge`. To instrument the OpenAI client, wrap it with `Sentry.instrumentOpenAiClient` and set recording settings. ```js import * as Sentry from '@sentry/cloudflare'; import OpenAI from 'openai'; const openai = new OpenAI(); const client = Sentry.instrumentOpenAiClient(openai, { recordInputs: true, recordOutputs: true }); // use the wrapped client ```
andreiborza
requested review from
AbhiPrasad,
Lms24,
RulaKhaled,
chargome,
mydea and
s1gr1d
|
can we do the changelog changes in a separate PR? 😅 makes it hard to follow along IMHO. Actually, I would probably not do that now anyhow, but wait until we have a reasonable amount of v10 releases that make the changelog too large, and only then extract the old ones out! |
AbhiPrasad
approved these changes
Aug 6, 2025
size-limit report 📦
|
what would be a good definition for too large? I extracted it out mainly so that I wasn't burning through context when feeding the changelog into cursor or claude code. |
s1gr1d
approved these changes
Aug 6, 2025
andreiborza
force-pushed
the
prepare-release/10.2.0
branch
from
120deb5 to
bcbb6af
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
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.