-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency sentry-sdk to v2.16.0 #49
base: main
Are you sure you want to change the base?
Conversation
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: pypi/[email protected] |
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #49 +/- ##
=======================================
Coverage 46.92% 46.92%
=======================================
Files 6 6
Lines 130 130
=======================================
Hits 61 61
Misses 69 69 ☔ View full report in Codecov by Sentry. |
This PR contains the following updates:
==2.15.0
->==2.16.0
Release Notes
getsentry/sentry-python (sentry-sdk)
v2.16.0
Compare Source
Integrations
Bottle: Add
failed_request_status_codes
(#3618) by @szokeasaurusrexYou can now define a set of integers that will determine which status codes
should be reported to Sentry.
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 @nijelDjango: Add
SpotlightMiddleware
when Spotlight is enabled (#3600) by @BYKDjango: Open relevant error when
SpotlightMiddleware
is on (#3614) by @BYKDjango: Support
http_methods_to_capture
in ASGI Django (#3607) by @sentrivanaASGI 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
andHEAD
are not included by default.Here's how to use it:
Miscellaneous
sample_rate
in DSC (and add explanatory tests) (#3603) by @antonpirkerhttpcore
basedHTTP2Transport
(#3588) by @BYK__notes__
support (#3620) by @szokeasaurusrexcodecov/codecov-action
from4.5.0
to4.6.0
(#3617) by @dependabotConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.