Comparing changes

The `attach_stacktrace` option was attaching stack traces to transactions. This is an expensive operation but the results aren't used anywhere.

…#4710) Bumps [actions/create-github-app-token](https://github.com/actions/create-github-app-token) from 2.1.0 to 2.1.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/create-github-app-token/releases">actions/create-github-app-token's releases</a>.</em></p> <blockquote> <h2>v2.1.1</h2> <h2><a href="https://github.com/actions/create-github-app-token/compare/v2.1.0...v2.1.1">2.1.1</a> (2025-08-11)</h2> <h3>Bug Fixes</h3> <ul> <li>revert "use <code>node24</code> as runner" (<a href="https://redirect.github.com/actions/create-github-app-token/issues/278">#278</a>) (<a href="https://github.com/actions/create-github-app-token/commit/5204204e81cbd981afcdf714413410ba8697fd67">5204204</a>), closes <a href="https://redirect.github.com/actions/create-github-app-token/issues/267">actions/create-github-app-token#267</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/create-github-app-token/commit/a8d616148505b5069dccd32f177bb87d7f39123b"><code>a8d6161</code></a> build(release): 2.1.1 [skip ci]</li> <li><a href="https://github.com/actions/create-github-app-token/commit/5204204e81cbd981afcdf714413410ba8697fd67"><code>5204204</code></a> fix: revert "use <code>node24</code> as runner" (<a href="https://redirect.github.com/actions/create-github-app-token/issues/278">#278</a>)</li> <li>See full diff in <a href="https://github.com/actions/create-github-app-token/compare/0f859bf9e69e887678d5bbfbee594437cb440ffe...a8d616148505b5069dccd32f177bb87d7f39123b">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions/create-github-app-token&package-manager=github_actions&previous-version=2.1.0&new-version=2.1.1)](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>

It looks like we're running into #4718 (and probably #4690) because the different agent runs are not properly isolated. This only seems to be a problem when multiple agent runs are awaited at once (e.g. via `asyncio.gather`) -- it seems that leads to some scope bleed. ```python import asyncio import sentry_sdk from agents import Agent, Runner from sentry_sdk.integrations.asyncio import AsyncioIntegration from sentry_sdk.integrations.openai_agents import OpenAIAgentsIntegration sentry_sdk.init(...) main_agent = Agent( name="main_agent", model="gpt-5", ) async def run_agent() -> None: runner = await Runner.run( starting_agent=main_agent, input="How are you?", ) print(runner.final_output) async def main() -> None: await asyncio.gather(*[run_agent() for _ in range(2)]) # throws an error # await asyncio.gather(run_agent()) # works ```

Commits on Aug 14, 2025

Merge branch 'release/2.35.0'

getsentry-bot committed Aug 14, 2025

Configuration menu

View commit details

Copy full SHA for e012ff1

Browse repository at this point

Copy the full SHA

e012ff1 View commit details

Browse the repository at this point in the history

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Comparing changes

Open a pull request

Commits on Aug 14, 2025

Commits on Aug 20, 2025

Commits on Aug 25, 2025

Commits on Aug 26, 2025

This comparison is taking too long to generate.

Uh oh!