chore(pip-prod)(deps): bump sentry-sdk from 2.15.0 to 2.16.0 #383

2024-10-10T18:03:39+02:00

dependabot[bot] commented

2024-10-10 18:03:39 +02:00

(Migrated from github.com)

Bumps sentry-sdk from 2.15.0 to 2.16.0.

Release notes

2.16.0

Integrations
Bottle: Add failed_request_status_codes (#3618) by @szokeasaurusrex

You can now define a set of integers that will determine which status codes should be reported to Sentry.
sentry_sdk.init(
    integrations=[
        BottleIntegration(
            failed_request_status_codes={403, *range(500, 600)},
        )
    ]
)
Examples of valid failed_request_status_codes:

{500} will only send events on HTTP 500.

{400, *range(500, 600)} will send events on HTTP 400 as well as the 5xx range.

{500, 503} will send events on HTTP 500 and 503.

set() (the empty set) will not send events for any HTTP status code.

The default is {*range(500, 600)}, meaning that all 5xx status codes are reported to Sentry.
Bottle: Delete never-reached code (#3605) by @szokeasaurusrex

Redis: Remove flaky test (#3626) by @sentrivana

Django: Improve getting psycopg3 connection info (#3580) by @nijel

Django: Add SpotlightMiddleware when Spotlight is enabled (#3600) by @BYK

Django: Open relevant error when SpotlightMiddleware is on (#3614) by @BYK
Django: Support http_methods_to_capture in ASGI Django (#3607) by @sentrivana

ASGI Django now also supports the http_methods_to_capture integration option. This is a configurable tuple of HTTP method verbs that should create a transaction in Sentry. The default is ("CONNECT", "DELETE", "GET", "PATCH", "POST", "PUT", "TRACE",). OPTIONS and HEAD are not included by default.

Here's how to use it:
sentry_sdk.init(
    integrations=[
        DjangoIntegration(
            http_methods_to_capture=("GET", "POST"),
        ),
    ],
)
Miscellaneous

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.16.0

Integrations
Bottle: Add failed_request_status_codes (#3618) by @szokeasaurusrex

You can now define a set of integers that will determine which status codes should be reported to Sentry.
sentry_sdk.init(
    integrations=[
        BottleIntegration(
            failed_request_status_codes={403, *range(500, 600)},
        )
    ]
)
Examples of valid failed_request_status_codes:

{500} will only send events on HTTP 500.

{400, *range(500, 600)} will send events on HTTP 400 as well as the 5xx range.

{500, 503} will send events on HTTP 500 and 503.

set() (the empty set) will not send events for any HTTP status code.

The default is {*range(500, 600)}, meaning that all 5xx status codes are reported to Sentry.
Bottle: Delete never-reached code (#3605) by @szokeasaurusrex

Redis: Remove flaky test (#3626) by @sentrivana

Django: Improve getting psycopg3 connection info (#3580) by @nijel

Django: Add SpotlightMiddleware when Spotlight is enabled (#3600) by @BYK

Django: Open relevant error when SpotlightMiddleware is on (#3614) by @BYK
Django: Support http_methods_to_capture in ASGI Django (#3607) by @sentrivana

ASGI Django now also supports the http_methods_to_capture integration option. This is a configurable tuple of HTTP method verbs that should create a transaction in Sentry. The default is ("CONNECT", "DELETE", "GET", "PATCH", "POST", "PUT", "TRACE",). OPTIONS and HEAD are not included by default.

Here's how to use it:
sentry_sdk.init(
    integrations=[
        DjangoIntegration(
            http_methods_to_capture=("GET", "POST"),
        ),
    ],
)
Miscellaneous

... (truncated)

Commits

9098601 Fix changelog formatting
b731910 Update CHANGELOG.md
0df20a7 release: 2.16.0
01b4687 Remove flaky test (#3626)
3945fc1 Add 3.13 to setup.py (#3574)
c110ff3 Add 3.13 to basepython (#3589)
d0eca65 feat(bottle): Add failed_request_status_codes (#3618)
d34c99a feat: Add opportunistic Brotli compression (#3612)
4f79aec fix(django): improve getting psycopg3 connection info (#3580)
2d2e548 feat: Add __notes__ support (#3620)
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)

Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 2.15.0 to 2.16.0. <details> <summary>Release notes</summary> Sourced from <a href="https://github.com/getsentry/sentry-python/releases">sentry-sdk's releases</a>. <blockquote> <h2>2.16.0</h2> <h3>Integrations</h3> <ul> <li> Bottle: Add <code>failed_request_status_codes</code> (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3618">#3618</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a> You can now define a set of integers that will determine which status codes should be reported to Sentry. <pre lang="python"><code>sentry_sdk.init( integrations=[ BottleIntegration( failed_request_status_codes={403, *range(500, 600)}, ) ] ) </code></pre> Examples of valid <code>failed_request_status_codes</code>: <ul> <li><code>{500}</code> will only send events on HTTP 500.</li> <li><code>{400, *range(500, 600)}</code> will send events on HTTP 400 as well as the 5xx range.</li> <li><code>{500, 503}</code> will send events on HTTP 500 and 503.</li> <li><code>set()</code> (the empty set) will not send events for any HTTP status code.</li> </ul> The default is <code>{*range(500, 600)}</code>, meaning that all 5xx status codes are reported to Sentry. </li> <li> Bottle: Delete never-reached code (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3605">#3605</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a> </li> <li> Redis: Remove flaky test (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3626">#3626</a>) by <a href="https://github.com/sentrivana"><code>@sentrivana</code></a> </li> <li> Django: Improve getting <code>psycopg3</code> connection info (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3580">#3580</a>) by <a href="https://github.com/nijel"><code>@nijel</code></a> </li> <li> Django: Add <code>SpotlightMiddleware</code> when Spotlight is enabled (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3600">#3600</a>) by <a href="https://github.com/BYK"><code>@BYK</code></a> </li> <li> Django: Open relevant error when <code>SpotlightMiddleware</code> is on (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3614">#3614</a>) by <a href="https://github.com/BYK"><code>@BYK</code></a> </li> <li> Django: Support <code>http_methods_to_capture</code> in ASGI Django (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3607">#3607</a>) by <a href="https://github.com/sentrivana"><code>@sentrivana</code></a> ASGI Django now also supports the <code>http_methods_to_capture</code> integration option. This is a configurable tuple of HTTP method verbs that should create a transaction in Sentry. The default is <code>("CONNECT", "DELETE", "GET", "PATCH", "POST", "PUT", "TRACE",)</code>. <code>OPTIONS</code> and <code>HEAD</code> are not included by default. Here's how to use it: <pre lang="python"><code>sentry_sdk.init( integrations=[ DjangoIntegration( http_methods_to_capture=("GET", "POST"), ), ], ) </code></pre> </li> </ul> <h3>Miscellaneous</h3>  </blockquote> ... (truncated) </details> <details> <summary>Changelog</summary> Sourced from <a href="https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md">sentry-sdk's changelog</a>. <blockquote> <h2>2.16.0</h2> <h3>Integrations</h3> <ul> <li> Bottle: Add <code>failed_request_status_codes</code> (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3618">#3618</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a> You can now define a set of integers that will determine which status codes should be reported to Sentry. <pre lang="python"><code>sentry_sdk.init( integrations=[ BottleIntegration( failed_request_status_codes={403, *range(500, 600)}, ) ] ) </code></pre> Examples of valid <code>failed_request_status_codes</code>: <ul> <li><code>{500}</code> will only send events on HTTP 500.</li> <li><code>{400, *range(500, 600)}</code> will send events on HTTP 400 as well as the 5xx range.</li> <li><code>{500, 503}</code> will send events on HTTP 500 and 503.</li> <li><code>set()</code> (the empty set) will not send events for any HTTP status code.</li> </ul> The default is <code>{*range(500, 600)}</code>, meaning that all 5xx status codes are reported to Sentry. </li> <li> Bottle: Delete never-reached code (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3605">#3605</a>) by <a href="https://github.com/szokeasaurusrex"><code>@szokeasaurusrex</code></a> </li> <li> Redis: Remove flaky test (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3626">#3626</a>) by <a href="https://github.com/sentrivana"><code>@sentrivana</code></a> </li> <li> Django: Improve getting <code>psycopg3</code> connection info (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3580">#3580</a>) by <a href="https://github.com/nijel"><code>@nijel</code></a> </li> <li> Django: Add <code>SpotlightMiddleware</code> when Spotlight is enabled (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3600">#3600</a>) by <a href="https://github.com/BYK"><code>@BYK</code></a> </li> <li> Django: Open relevant error when <code>SpotlightMiddleware</code> is on (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3614">#3614</a>) by <a href="https://github.com/BYK"><code>@BYK</code></a> </li> <li> Django: Support <code>http_methods_to_capture</code> in ASGI Django (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3607">#3607</a>) by <a href="https://github.com/sentrivana"><code>@sentrivana</code></a> ASGI Django now also supports the <code>http_methods_to_capture</code> integration option. This is a configurable tuple of HTTP method verbs that should create a transaction in Sentry. The default is <code>("CONNECT", "DELETE", "GET", "PATCH", "POST", "PUT", "TRACE",)</code>. <code>OPTIONS</code> and <code>HEAD</code> are not included by default. Here's how to use it: <pre lang="python"><code>sentry_sdk.init( integrations=[ DjangoIntegration( http_methods_to_capture=("GET", "POST"), ), ], ) </code></pre> </li> </ul> <h3>Miscellaneous</h3>  </blockquote> ... (truncated) </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-python/commit/90986018b8512831313636a3aae8afc8fe2f02d7"><code>9098601</code></a> Fix changelog formatting</li> <li><a href="https://github.com/getsentry/sentry-python/commit/b73191073b7c8e371a21461ae57a0b97f1c4de00"><code>b731910</code></a> Update CHANGELOG.md</li> <li><a href="https://github.com/getsentry/sentry-python/commit/0df20a76a4c8f2ac4deea461038ebc479394c14d"><code>0df20a7</code></a> release: 2.16.0</li> <li><a href="https://github.com/getsentry/sentry-python/commit/01b468724ad63b814c742eb57053fa1e46d7f34f"><code>01b4687</code></a> Remove flaky test (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3626">#3626</a>)</li> <li><a href="https://github.com/getsentry/sentry-python/commit/3945fc118f2fbc3809a1d32e4782e54f445cb882"><code>3945fc1</code></a> Add 3.13 to setup.py (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3574">#3574</a>)</li> <li><a href="https://github.com/getsentry/sentry-python/commit/c110ff38435d2707bcfe19ff164307ff41c20196"><code>c110ff3</code></a> Add 3.13 to basepython (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3589">#3589</a>)</li> <li><a href="https://github.com/getsentry/sentry-python/commit/d0eca65aa155a3a6e391b013e6b30ed9e0e3ad23"><code>d0eca65</code></a> feat(bottle): Add <code>failed_request_status_codes</code> (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3618">#3618</a>)</li> <li><a href="https://github.com/getsentry/sentry-python/commit/d34c99af365bf020af561d47b689da5abbb5c7d7"><code>d34c99a</code></a> feat: Add opportunistic Brotli compression (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3612">#3612</a>)</li> <li><a href="https://github.com/getsentry/sentry-python/commit/4f79aecf935fcc2c4728ae15368cac9a10687d9f"><code>4f79aec</code></a> fix(django): improve getting psycopg3 connection info (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3580">#3580</a>)</li> <li><a href="https://github.com/getsentry/sentry-python/commit/2d2e5488172972498aec5c2eaf8a0ba62937e840"><code>2d2e548</code></a> feat: Add <code>__notes__</code> support (<a href="https://redirect.github.com/getsentry/sentry-python/issues/3620">#3620</a>)</li> <li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-python/compare/2.15.0...2.16.0">compare view</a></li> </ul> </details> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sentry-sdk&package-manager=pip&previous-version=2.15.0&new-version=2.16.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> 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-10-10 18:03:39 +02:00

sonarqubecloud[bot] commented

2024-10-10 18:04:58 +02:00

(Migrated from github.com)

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

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_webexmemebot&pullRequest=383) **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_webexmemebot&pullRequest=383&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true) ![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/accepted-16px.png '') [0 Accepted issues](https://sonarcloud.io/project/issues?id=luketainton_webexmemebot&pullRequest=383&issueStatuses=ACCEPTED) 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_webexmemebot&pullRequest=383&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true) ![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/passed-16px.png '') [0.0% Coverage on New Code](https://sonarcloud.io/component_measures?id=luketainton_webexmemebot&pullRequest=383&metric=new_coverage&view=list) ![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/passed-16px.png '') [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=luketainton_webexmemebot&pullRequest=383&metric=new_duplicated_lines_density&view=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=luketainton_webexmemebot&pullRequest=383)

Sign in to join this conversation.

No reviewers

luketainton