build(deps): bump sentry-sdk from 1.5.8 to 2.0.1

[dependabot]

Bumps sentry-sdk from 1.5.8 to 2.0.1.

Release notes

Sourced from sentry-sdk's releases.

2.0.1

Various fixes & improvements

• Fix: Do not use convenience decorator (#3022) by @​sentrivana
• Refactoring propagation context (#2970) by @​antonpirker
• Use pid for test database name in Django tests (#2998) by @​antonpirker
• Remove outdated RC mention in docs (#3018) by @​sentrivana
• Delete inaccurate comment from docs (#3002) by @​szokeasaurusrex
• Add Lambda function that deletes test Lambda functions (#2960) by @​antonpirker
• Correct discarded transaction debug message (#3002) by @​szokeasaurusrex
• Add tests for discarded transaction debug messages (#3002) by @​szokeasaurusrex
• Fix comment typo in metrics (#2992) by @​szokeasaurusrex
• build(deps): bump actions/checkout from 4.1.1 to 4.1.4 (#3011) by @​dependabot
• build(deps): bump checkouts/data-schemas from 1e17eb5 to 4aa14a7 (#2997) by @​dependabot

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(...)

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.0.1

Various fixes & improvements

• Fix: Do not use convenience decorator (#3022) by @​sentrivana
• Refactoring propagation context (#2970) by @​antonpirker
• Use pid for test database name in Django tests (#2998) by @​antonpirker
• Remove outdated RC mention in docs (#3018) by @​sentrivana
• Delete inaccurate comment from docs (#3002) by @​szokeasaurusrex
• Add Lambda function that deletes test Lambda functions (#2960) by @​antonpirker
• Correct discarded transaction debug message (#3002) by @​szokeasaurusrex
• Add tests for discarded transaction debug messages (#3002) by @​szokeasaurusrex
• Fix comment typo in metrics (#2992) by @​szokeasaurusrex
• build(deps): bump actions/checkout from 4.1.1 to 4.1.4 (#3011) by @​dependabot
• build(deps): bump checkouts/data-schemas from 1e17eb5 to 4aa14a7 (#2997) by @​dependabot

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:

... (truncated)

Commits

• 882ed7f Updated changelog
• ce89048 release: 2.0.1
• 162773c fix(integrations): Do not use convenience decorator (#3022)
• a626f01 Add Lambda function that deletes test Lambda functions (#2960)
• f5db9ce Refactoring propagation context (#2970)
• d91a510 Use pid for test database name in Django tests (#2998)
• 534a301 test(tracing): Add tests for discarded transaction debug messages
• 5aa7c9b fix(tracing): Correct discarded transaction debug message
• bda9deb docs(tracing): Delete inaccurate comment
• 6a73368 build(deps): bump checkouts/data-schemas from 1e17eb5 to 4aa14a7 (#2997)
• Additional commits viewable in compare view

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)

[dependabot]

Superseded by #297.