Bump sentry-sdk from 0.19.5 to 1.1.0

[dependabot-preview]

⚠️ Dependabot Preview has been deactivated ⚠️

This pull request was created by Dependabot Preview, and you've upgraded to Dependabot. This means it won't respond to dependabot commands nor will it be automatically closed if a new version is found.

If you close this pull request, Dependabot will re-create it the next time it checks for updates and everything will work as expected.

---

Bumps sentry-sdk from 0.19.5 to 1.1.0.

Release notes

Sourced from sentry-sdk's releases.

1.1.0

• Fix for AWSLambda integration returns value of original handler #1106
• Fix for RQ integration that only captures exception if RQ job has failed and ignore retries #1076
• Feature that supports Tracing for the Tornado integration #1060
• Feature that supports wild cards in ignore_logger in the Logging Integration #1053
• Fix for django that deals with template span description names that are either lists or tuples #1054

1.0.0

This release contains a breaking change

• BREAKING CHANGE: Feat: Moved auto_session_tracking experimental flag to a proper option and removed explicitly setting experimental session_mode in favor of auto detecting its value, hence enabling release health by default #994
• Fixed Django transaction name by setting the name to request.path_info rather than request.path
• Fix for tracing by getting HTTP headers from span rather than transaction when possible #1035
• Fix for Flask transactions missing request body in non errored transactions #1034
• Fix for honoring the X-Forwarded-For header #1037
• Fix for worker that logs data dropping of events with level error #1032

0.20.3

• Added scripts to support auto instrumentation of no code AWS lambda Python functions

0.20.2

• Fix incorrect regex in craft to include wheel file in pypi release

0.20.1

• Fix for error that occurs with Async Middlewares when the middleware is a function rather than a class

0.20.0

• Fix for header extraction for AWS lambda/API extraction
• Fix multiple **kwargs type hints # 967
• Fix that corrects AWS lambda integration failure to detect the aws-lambda-ric 1.0 bootstrap #976
• Fix AWSLambda integration: variable "timeout_thread" referenced before assignment #977
• Use full git sha as release name #960
• BREAKING CHANGE: The default environment is now production, not based on release
• Django integration now creates transaction spans for template rendering
• Fix headers not parsed correctly in ASGI middleware, Decode headers before creating transaction #984
• Restored ability to have tracing disabled #991
• Fix Django async views not behaving asynchronously
• Performance improvement: supported pre-aggregated sessions

Changelog

Sourced from sentry-sdk's changelog.

1.1.0

• Fix for AWSLambda integration returns value of original handler #1106
• Fix for RQ integration that only captures exception if RQ job has failed and ignore retries #1076
• Feature that supports Tracing for the Tornado integration #1060
• Feature that supports wild cards in ignore_logger in the Logging Integration #1053
• Fix for django that deals with template span description names that are either lists or tuples #1054

1.0.0

This release contains a breaking change

• BREAKING CHANGE: Feat: Moved auto_session_tracking experimental flag to a proper option and removed explicitly setting experimental session_mode in favor of auto detecting its value, hence enabling release health by default #994
• Fixed Django transaction name by setting the name to request.path_info rather than request.path
• Fix for tracing by getting HTTP headers from span rather than transaction when possible #1035
• Fix for Flask transactions missing request body in non errored transactions #1034
• Fix for honoring the X-Forwarded-For header #1037
• Fix for worker that logs data dropping of events with level error #1032

0.20.3

• Added scripts to support auto instrumentation of no code AWS lambda Python functions

0.20.2

• Fix incorrect regex in craft to include wheel file in pypi release

0.20.1

• Fix for error that occurs with Async Middlewares when the middleware is a function rather than a class

0.20.0

• Fix for header extraction for AWS lambda/API extraction
• Fix multiple **kwargs type hints # 967
• Fix that corrects AWS lambda integration failure to detect the aws-lambda-ric 1.0 bootstrap #976
• Fix AWSLambda integration: variable "timeout_thread" referenced before assignment #977
• Use full git sha as release name #960
• BREAKING CHANGE: The default environment is now production, not based on release
• Django integration now creates transaction spans for template rendering
• Fix headers not parsed correctly in ASGI middleware, Decode headers before creating transaction #984
• Restored ability to have tracing disabled #991
• Fix Django async views not behaving asynchronously
• Performance improvement: supported pre-aggregated sessions

Commits

• 7822f2e release: 1.1.0
• 90ad89a fix(ci): Removed failing pypy-2.7 from CI (#1111)
• 059f334 docs: Fixed incorrect heading level on new release (#1110)
• f295117 Updated change log for new release 1.1 (#1108)
• f6ea27c Revert "fix(aws-lambda): Change function handler name to 'x.y' (#1107)" (#1109)
• 7c7bf31 fix(serverless): Return value from original handler (#1106)
• b7b5c03 fix(aws-lambda): Change function handler name to 'x.y' (#1107)
• 76aa189 fix(rq): Only capture exception if RQ job has failed (ignore retries) (#1076)
• d7cf16c chore: Fix CI failures (#1101)
• 927903e Update traces_sampler declaration to concrete types (#1091)
• 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 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[github-actions]

This PR introduces visual differences. Click here to inspect the diffs.

[dependabot-preview]

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.