This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
requirement: bump sentry-sdk from 2.14.0 to 2.16.0 (#409)
Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 2.14.0 to 2.16.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.16.0</h2> <h3>Integrations</h3> <ul> <li> <p>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></p> <p>You can now define a set of integers that will determine which status codes should be reported to Sentry.</p> <pre lang="python"><code>sentry_sdk.init( integrations=[ BottleIntegration( failed_request_status_codes={403, *range(500, 600)}, ) ] ) </code></pre> <p>Examples of valid <code>failed_request_status_codes</code>:</p> <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> <p>The default is <code>{*range(500, 600)}</code>, meaning that all 5xx status codes are reported to Sentry.</p> </li> <li> <p>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></p> </li> <li> <p>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></p> </li> <li> <p>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></p> </li> <li> <p>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></p> </li> <li> <p>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></p> </li> <li> <p>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></p> <p>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.</p> <p>Here's how to use it:</p> <pre lang="python"><code>sentry_sdk.init( integrations=[ DjangoIntegration( http_methods_to_capture=("GET", "POST"), ), ], ) </code></pre> </li> </ul> <h3>Miscellaneous</h3> <!-- 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.16.0</h2> <h3>Integrations</h3> <ul> <li> <p>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></p> <p>You can now define a set of integers that will determine which status codes should be reported to Sentry.</p> <pre lang="python"><code>sentry_sdk.init( integrations=[ BottleIntegration( failed_request_status_codes={403, *range(500, 600)}, ) ] ) </code></pre> <p>Examples of valid <code>failed_request_status_codes</code>:</p> <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> <p>The default is <code>{*range(500, 600)}</code>, meaning that all 5xx status codes are reported to Sentry.</p> </li> <li> <p>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></p> </li> <li> <p>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></p> </li> <li> <p>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></p> </li> <li> <p>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></p> </li> <li> <p>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></p> </li> <li> <p>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></p> <p>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.</p> <p>Here's how to use it:</p> <pre lang="python"><code>sentry_sdk.init( integrations=[ DjangoIntegration( http_methods_to_capture=("GET", "POST"), ), ], ) </code></pre> </li> </ul> <h3>Miscellaneous</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </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.14.0...2.16.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=2.14.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> <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] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information