repos/roboluke
3
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Releases 50 Activity

chore(pip-prod)(deps): bump sentry-sdk from 1.45.0 to 2.0.0 #193

Closed
dependabot[bot] wants to merge 1 commits from dependabot/pip/sentry-sdk-2.0.0 into next
pull from: dependabot/pip/sentry-sdk-2.0.0
merge into: repos:next
Conversation 3 Commits 1 Files Changed 1 +1 -1
dependabot[bot] commented 2024-04-25 18:11:47 +02:00 (Migrated from github.com)
Copy Link

Bumps sentry-sdk from 1.45.0 to 2.0.0.

Release notes

Sourced from sentry-sdk's releases.

2.0.0

This is the first major update in a long time!

We dropped support for some ancient languages and frameworks (Yes, Python 2.7 is no longer supported). Additionally we refactored a big part of the foundation of the SDK (how data inside the SDK is handled).

We hope you like it!

For a shorter version of what you need to do, to upgrade to Sentry SDK 2.0 see: https://docs.sentry.io/platforms/python/migration/1.x-to-2.x

New Features

  • Additional integrations will now be activated automatically if the SDK detects the respective package is installed: Ariadne, ARQ, asyncpg, Chalice, clickhouse-driver, GQL, Graphene, huey, Loguru, PyMongo, Quart, Starlite, Strawberry.
  • Added new API for custom instrumentation: new_scope, isolation_scope. See the Deprecated section to see how they map to the existing APIs.

Changed

(These changes are all backwards-incompatible. Breaking Change (if you are just skimming for that phrase))

  • The Pyramid integration will not capture errors that might happen in authenticated_userid() in a custom AuthenticationPolicy class.

  • The method need_code_loation of the MetricsAggregator was renamed to need_code_location.

  • The BackgroundWorker thread used to process events was renamed from raven-sentry.BackgroundWorker to sentry-sdk.BackgroundWorker.

  • The reraise function was moved from sentry_sdk._compat to sentry_sdk.utils.

  • The _ScopeManager was moved from sentry_sdk.hub to sentry_sdk.scope.

  • Moved the contents of tracing_utils_py3.py to tracing_utils.py. The start_child_span_decorator is now in sentry_sdk.tracing_utils.

  • The actual implementation of get_current_span was moved to sentry_sdk.tracing_utils. sentry_sdk.get_current_span is still accessible as part of the top-level API.

  • sentry_sdk.tracing_utils.add_query_source(): Removed the hub parameter. It is not necessary anymore.

  • sentry_sdk.tracing_utils.record_sql_queries(): Removed the hub parameter. It is not necessary anymore.

  • sentry_sdk.tracing_utils.get_current_span() does now take a scope instead of a hub as parameter.

  • sentry_sdk.tracing_utils.should_propagate_trace() now takes a Client instead of a Hub as first parameter.

  • sentry_sdk.utils.is_sentry_url() now takes a Client instead of a Hub as first parameter.

  • sentry_sdk.utils._get_contextvars does not return a tuple with three values, but a tuple with two values. The copy_context was removed.

  • If you create a transaction manually and later mutate the transaction in a configure_scope block this does not work anymore. Here is a recipe on how to change your code to make it work: Your existing implementation:

    transaction = sentry_sdk.transaction(...)

    later in the code execution:
    

    with sentry_sdk.configure_scope() as scope:
scope.set_transaction_name("new-transaction-name")

    needs to be changed to this:

    transaction = sentry_sdk.transaction(...)

    later in the code execution:
    

    scope = sentry_sdk.Scope.get_current_scope()
scope.set_transaction_name("new-transaction-name")

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.0.0

This is the first major update in a long time!

We dropped support for some ancient languages and frameworks (Yes, Python 2.7 is no longer supported). Additionally we refactored a big part of the foundation of the SDK (how data inside the SDK is handled).

We hope you like it!

For a shorter version of what you need to do, to upgrade to Sentry SDK 2.0 see: https://docs.sentry.io/platforms/python/migration/1.x-to-2.x

New Features

  • Additional integrations will now be activated automatically if the SDK detects the respective package is installed: Ariadne, ARQ, asyncpg, Chalice, clickhouse-driver, GQL, Graphene, huey, Loguru, PyMongo, Quart, Starlite, Strawberry.
  • Added new API for custom instrumentation: new_scope, isolation_scope. See the Deprecated section to see how they map to the existing APIs.

Changed

(These changes are all backwards-incompatible. Breaking Change (if you are just skimming for that phrase))

  • The Pyramid integration will not capture errors that might happen in authenticated_userid() in a custom AuthenticationPolicy class.

  • The method need_code_loation of the MetricsAggregator was renamed to need_code_location.

  • The BackgroundWorker thread used to process events was renamed from raven-sentry.BackgroundWorker to sentry-sdk.BackgroundWorker.

  • The reraise function was moved from sentry_sdk._compat to sentry_sdk.utils.

  • The _ScopeManager was moved from sentry_sdk.hub to sentry_sdk.scope.

  • Moved the contents of tracing_utils_py3.py to tracing_utils.py. The start_child_span_decorator is now in sentry_sdk.tracing_utils.

  • The actual implementation of get_current_span was moved to sentry_sdk.tracing_utils. sentry_sdk.get_current_span is still accessible as part of the top-level API.

  • sentry_sdk.tracing_utils.add_query_source(): Removed the hub parameter. It is not necessary anymore.

  • sentry_sdk.tracing_utils.record_sql_queries(): Removed the hub parameter. It is not necessary anymore.

  • sentry_sdk.tracing_utils.get_current_span() does now take a scope instead of a hub as parameter.

  • sentry_sdk.tracing_utils.should_propagate_trace() now takes a Client instead of a Hub as first parameter.

  • sentry_sdk.utils.is_sentry_url() now takes a Client instead of a Hub as first parameter.

  • sentry_sdk.utils._get_contextvars does not return a tuple with three values, but a tuple with two values. The copy_context was removed.

  • If you create a transaction manually and later mutate the transaction in a configure_scope block this does not work anymore. Here is a recipe on how to change your code to make it work: Your existing implementation:

    transaction = sentry_sdk.transaction(...)

    later in the code execution:
    

    with sentry_sdk.configure_scope() as scope:
scope.set_transaction_name("new-transaction-name")

    needs to be changed to this:

    transaction = sentry_sdk.transaction(...)

    later in the code execution:
    

    scope = sentry_sdk.Scope.get_current_scope()
scope.set_transaction_name("new-transaction-name")

... (truncated)

Commits
  • 38bbb8d Updated changelog
  • abca568 Updated changelog
  • 0b454c0 Updated changelog
  • 2642c8a Updated changelog
  • cc1dbc0 release: 2.0.0
  • 74310f0 Merge branch 'release/2.0.0rc6' into sentry-sdk-2.0
  • 62d4c48 release: 2.0.0rc6
  • 17715c0 Restore original behavior by always creating a span (#3005)
  • 7ef20df Merge baggage headers (incoming and new created ones) (#3001)
  • 9fc2f44 Fix duplicate baggage headers in Celery integration introduced in SDK 2.0 (#2...
  • Additional commits viewable in compare view

Dependabot compatibility score

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)
Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 1.45.0 to 2.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-python/releases">sentry-sdk's releases</a>.</em></p> <blockquote> <h2>2.0.0</h2> <p>This is the first major update in a <em>long</em> time!</p> <p>We dropped support for some ancient languages and frameworks (Yes, Python 2.7 is no longer supported). Additionally we refactored a big part of the foundation of the SDK (how data inside the SDK is handled).</p> <p>We hope you like it!</p> <p>For a shorter version of what you need to do, to upgrade to Sentry SDK 2.0 see: <a href="https://docs.sentry.io/platforms/python/migration/1.x-to-2.x">https://docs.sentry.io/platforms/python/migration/1.x-to-2.x</a></p> <h3>New Features</h3> <ul> <li>Additional integrations will now be activated automatically if the SDK detects the respective package is installed: Ariadne, ARQ, asyncpg, Chalice, clickhouse-driver, GQL, Graphene, huey, Loguru, PyMongo, Quart, Starlite, Strawberry.</li> <li>Added new API for custom instrumentation: <code>new_scope</code>, <code>isolation_scope</code>. See the <a href="https://github.com/getsentry/sentry-python/blob/HEAD/#deprecated">Deprecated</a> section to see how they map to the existing APIs.</li> </ul> <h3>Changed</h3> <p>(These changes are all backwards-incompatible. <strong>Breaking Change</strong> (if you are just skimming for that phrase))</p> <ul> <li> <p>The Pyramid integration will not capture errors that might happen in <code>authenticated_userid()</code> in a custom <code>AuthenticationPolicy</code> class.</p> </li> <li> <p>The method <code>need_code_loation</code> of the <code>MetricsAggregator</code> was renamed to <code>need_code_location</code>.</p> </li> <li> <p>The <code>BackgroundWorker</code> thread used to process events was renamed from <code>raven-sentry.BackgroundWorker</code> to <code>sentry-sdk.BackgroundWorker</code>.</p> </li> <li> <p>The <code>reraise</code> function was moved from <code>sentry_sdk._compat</code> to <code>sentry_sdk.utils</code>.</p> </li> <li> <p>The <code>_ScopeManager</code> was moved from <code>sentry_sdk.hub</code> to <code>sentry_sdk.scope</code>.</p> </li> <li> <p>Moved the contents of <code>tracing_utils_py3.py</code> to <code>tracing_utils.py</code>. The <code>start_child_span_decorator</code> is now in <code>sentry_sdk.tracing_utils</code>.</p> </li> <li> <p>The actual implementation of <code>get_current_span</code> was moved to <code>sentry_sdk.tracing_utils</code>. <code>sentry_sdk.get_current_span</code> is still accessible as part of the top-level API.</p> </li> <li> <p><code>sentry_sdk.tracing_utils.add_query_source()</code>: Removed the <code>hub</code> parameter. It is not necessary anymore.</p> </li> <li> <p><code>sentry_sdk.tracing_utils.record_sql_queries()</code>: Removed the <code>hub</code> parameter. It is not necessary anymore.</p> </li> <li> <p><code>sentry_sdk.tracing_utils.get_current_span()</code> does now take a <code>scope</code> instead of a <code>hub</code> as parameter.</p> </li> <li> <p><code>sentry_sdk.tracing_utils.should_propagate_trace()</code> now takes a <code>Client</code> instead of a <code>Hub</code> as first parameter.</p> </li> <li> <p><code>sentry_sdk.utils.is_sentry_url()</code> now takes a <code>Client</code> instead of a <code>Hub</code> as first parameter.</p> </li> <li> <p><code>sentry_sdk.utils._get_contextvars</code> does not return a tuple with three values, but a tuple with two values. The <code>copy_context</code> was removed.</p> </li> <li> <p>If you create a transaction manually and later mutate the transaction in a <code>configure_scope</code> block this does not work anymore. Here is a recipe on how to change your code to make it work: Your existing implementation:</p> <pre lang="python"><code>transaction = sentry_sdk.transaction(...) <h1>later in the code execution:</h1> <p>with sentry_sdk.configure_scope() as scope: scope.set_transaction_name(&quot;new-transaction-name&quot;) </code></pre></p> <p>needs to be changed to this:</p> <pre lang="python"><code>transaction = sentry_sdk.transaction(...) <h1>later in the code execution:</h1> <p>scope = sentry_sdk.Scope.get_current_scope() scope.set_transaction_name(&quot;new-transaction-name&quot;) </code></pre></p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md">sentry-sdk's changelog</a>.</em></p> <blockquote> <h2>2.0.0</h2> <p>This is the first major update in a <em>long</em> time!</p> <p>We dropped support for some ancient languages and frameworks (Yes, Python 2.7 is no longer supported). Additionally we refactored a big part of the foundation of the SDK (how data inside the SDK is handled).</p> <p>We hope you like it!</p> <p>For a shorter version of what you need to do, to upgrade to Sentry SDK 2.0 see: <a href="https://docs.sentry.io/platforms/python/migration/1.x-to-2.x">https://docs.sentry.io/platforms/python/migration/1.x-to-2.x</a></p> <h3>New Features</h3> <ul> <li>Additional integrations will now be activated automatically if the SDK detects the respective package is installed: Ariadne, ARQ, asyncpg, Chalice, clickhouse-driver, GQL, Graphene, huey, Loguru, PyMongo, Quart, Starlite, Strawberry.</li> <li>Added new API for custom instrumentation: <code>new_scope</code>, <code>isolation_scope</code>. See the <a href="https://github.com/getsentry/sentry-python/blob/master/#deprecated">Deprecated</a> section to see how they map to the existing APIs.</li> </ul> <h3>Changed</h3> <p>(These changes are all backwards-incompatible. <strong>Breaking Change</strong> (if you are just skimming for that phrase))</p> <ul> <li> <p>The Pyramid integration will not capture errors that might happen in <code>authenticated_userid()</code> in a custom <code>AuthenticationPolicy</code> class.</p> </li> <li> <p>The method <code>need_code_loation</code> of the <code>MetricsAggregator</code> was renamed to <code>need_code_location</code>.</p> </li> <li> <p>The <code>BackgroundWorker</code> thread used to process events was renamed from <code>raven-sentry.BackgroundWorker</code> to <code>sentry-sdk.BackgroundWorker</code>.</p> </li> <li> <p>The <code>reraise</code> function was moved from <code>sentry_sdk._compat</code> to <code>sentry_sdk.utils</code>.</p> </li> <li> <p>The <code>_ScopeManager</code> was moved from <code>sentry_sdk.hub</code> to <code>sentry_sdk.scope</code>.</p> </li> <li> <p>Moved the contents of <code>tracing_utils_py3.py</code> to <code>tracing_utils.py</code>. The <code>start_child_span_decorator</code> is now in <code>sentry_sdk.tracing_utils</code>.</p> </li> <li> <p>The actual implementation of <code>get_current_span</code> was moved to <code>sentry_sdk.tracing_utils</code>. <code>sentry_sdk.get_current_span</code> is still accessible as part of the top-level API.</p> </li> <li> <p><code>sentry_sdk.tracing_utils.add_query_source()</code>: Removed the <code>hub</code> parameter. It is not necessary anymore.</p> </li> <li> <p><code>sentry_sdk.tracing_utils.record_sql_queries()</code>: Removed the <code>hub</code> parameter. It is not necessary anymore.</p> </li> <li> <p><code>sentry_sdk.tracing_utils.get_current_span()</code> does now take a <code>scope</code> instead of a <code>hub</code> as parameter.</p> </li> <li> <p><code>sentry_sdk.tracing_utils.should_propagate_trace()</code> now takes a <code>Client</code> instead of a <code>Hub</code> as first parameter.</p> </li> <li> <p><code>sentry_sdk.utils.is_sentry_url()</code> now takes a <code>Client</code> instead of a <code>Hub</code> as first parameter.</p> </li> <li> <p><code>sentry_sdk.utils._get_contextvars</code> does not return a tuple with three values, but a tuple with two values. The <code>copy_context</code> was removed.</p> </li> <li> <p>If you create a transaction manually and later mutate the transaction in a <code>configure_scope</code> block this does not work anymore. Here is a recipe on how to change your code to make it work: Your existing implementation:</p> <pre lang="python"><code>transaction = sentry_sdk.transaction(...) <h1>later in the code execution:</h1> <p>with sentry_sdk.configure_scope() as scope: scope.set_transaction_name(&quot;new-transaction-name&quot;) </code></pre></p> <p>needs to be changed to this:</p> <pre lang="python"><code>transaction = sentry_sdk.transaction(...) <h1>later in the code execution:</h1> <p>scope = sentry_sdk.Scope.get_current_scope() scope.set_transaction_name(&quot;new-transaction-name&quot;) </code></pre></p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-python/commit/38bbb8db423767ee4e046ec078756b7a1f575af4"><code>38bbb8d</code></a> Updated changelog</li> <li><a href="https://github.com/getsentry/sentry-python/commit/abca5680144533bb309d6cfe63166606f3d297a1"><code>abca568</code></a> Updated changelog</li> <li><a href="https://github.com/getsentry/sentry-python/commit/0b454c06f093991fcbbd495f1c28d115859b43db"><code>0b454c0</code></a> Updated changelog</li> <li><a href="https://github.com/getsentry/sentry-python/commit/2642c8a6570a993912569c8a53575c5c82c28e90"><code>2642c8a</code></a> Updated changelog</li> <li><a href="https://github.com/getsentry/sentry-python/commit/cc1dbc06df665cb8b088670122f57124f976e6da"><code>cc1dbc0</code></a> release: 2.0.0</li> <li><a href="https://github.com/getsentry/sentry-python/commit/74310f08e2aed7b796c14a77e061abbf5ad24a00"><code>74310f0</code></a> Merge branch 'release/2.0.0rc6' into sentry-sdk-2.0</li> <li><a href="https://github.com/getsentry/sentry-python/commit/62d4c4817b44c971995847c968d6751f9eb25676"><code>62d4c48</code></a> release: 2.0.0rc6</li> <li><a href="https://github.com/getsentry/sentry-python/commit/17715c049b9472d16b627c23432fadd3c05096ec"><code>17715c0</code></a> Restore original behavior by always creating a span (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3005">#3005</a>)</li> <li><a href="https://github.com/getsentry/sentry-python/commit/7ef20df18d139f41aea1b6d4685e2273a7b0f074"><code>7ef20df</code></a> Merge baggage headers (incoming and new created ones) (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3001">#3001</a>)</li> <li><a href="https://github.com/getsentry/sentry-python/commit/9fc2f44649a044af123497717e8690b24d62629b"><code>9fc2f44</code></a> Fix duplicate baggage headers in Celery integration introduced in SDK 2.0 (<a href="https://redirect.github.com/getsentry/sentry-python/issues/2">#2</a>...</li> <li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-python/compare/1.45.0...2.0.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sentry-sdk&package-manager=pip&previous-version=1.45.0&new-version=2.0.0)](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>
luketainton (Migrated from github.com) reviewed 2024-04-25 18:11:47 +02:00
sonarqubecloud[bot] commented 2024-04-25 18:13:02 +02:00 (Migrated from github.com)
Copy Link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

## [![Quality Gate Passed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadge/qg-passed-20px.png 'Quality Gate Passed')](https://sonarcloud.io/dashboard?id=luketainton_roboluke-tasks&pullRequest=193) **Quality Gate passed** Issues ![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/passed-16px.png '') [0 New issues](https://sonarcloud.io/project/issues?id=luketainton_roboluke-tasks&pullRequest=193&resolved=false&inNewCodePeriod=true) ![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/accepted-16px.png '') [0 Accepted issues](https://sonarcloud.io/component_measures?id=luketainton_roboluke-tasks&pullRequest=193&metric=new_accepted_issues&view=list) Measures ![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/passed-16px.png '') [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=luketainton_roboluke-tasks&pullRequest=193&resolved=false&inNewCodePeriod=true) ![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/no-data-16px.png '') No data about Coverage ![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/no-data-16px.png '') No data about Duplication [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=luketainton_roboluke-tasks&pullRequest=193)
dependabot[bot] commented 2024-04-26 18:08:35 +02:00 (Migrated from github.com)
Copy Link

Superseded by #195.

Superseded by #195.

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
luketainton
Labels
Clear labels
bug
Something isn't working
dependencies
Pull requests that update a dependency file
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
invalid
This doesn't seem right
question
Further information is requested
security
wontfix
This will not be worked on
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
dependencies
Milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: repos/roboluke#193
No description provided.
Delete Branch "dependabot/pip/sentry-sdk-2.0.0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?