build(deps-dev): update dependency sentry-sdk to v2.18.0 #405
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.14.0
->2.18.0
Release Notes
getsentry/sentry-python (sentry-sdk)
v2.18.0
Compare Source
Various fixes & improvements
http.client
span on timeout (#3723) by @Zylphrexh2
existence in HTTP/2 transport (#3690) by @BYKtype()
instead when extracting frames (#3716) by @Zylphrexpython_multipart
import overmultipart
(#3710) by @musicinmybrainpytest
fortornado-latest
tests (#3714) by @szokeasaurusrexpytest-asyncio
forredis
tests (Python 3.12-13) (#3706) by @szokeasaurusrexpytest
forcelery
tests (#3701) by @szokeasaurusrexpytest
on Python 3.8+gevent
tests (#3700) by @szokeasaurusrexpytest
for Python 3.8+common
tests (#3697) by @szokeasaurusrexpytest
pin inrequirements-devenv.txt
(#3696) by @szokeasaurusrexv2.17.0
Compare Source
Various fixes & improvements
ensure_integration_enabled_async
(#3632) by @sentrivanasphinx
(#3650) by @sentrivanaactions/checkout
from4.2.0
to4.2.1
(#3651) by @dependabotv2.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 @dependabotv2.15.0
Compare Source
Integrations
Configure HTTP methods to capture in ASGI/WSGI middleware and frameworks (#3531) by @antonpirker
We've added a new option to the Django, Flask, Starlette and FastAPI integrations called
http_methods_to_capture
. 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 (substitute Flask for your framework integration):
Django: Allow ASGI to use
drf_request
inDjangoRequestExtractor
(#3572) by @PakawiNzDjango: Don't let
RawPostDataException
bubble up (#3553) by @sentrivanaDjango: Add
sync_capable
toSentryWrappingMiddleware
(#3510) by @szokeasaurusrexAIOHTTP: Add
failed_request_status_codes
(#3551) 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.AIOHTTP: Delete test which depends on AIOHTTP behavior (#3568) by @szokeasaurusrex
AIOHTTP: Handle invalid responses (#3554) by @szokeasaurusrex
FastAPI/Starlette: Support new
failed_request_status_codes
(#3563) by @szokeasaurusrexThe format of
failed_request_status_codes
has changed from a listof integers and containers to a set:
The old way of defining
failed_request_status_codes
will continue to workfor the time being. Examples of valid new-style
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.FastAPI/Starlette: Fix
failed_request_status_codes=[]
(#3561) by @szokeasaurusrexFastAPI/Starlette: Remove invalid
failed_request_status_code
tests (#3560) by @szokeasaurusrexFastAPI/Starlette: Refactor shared test parametrization (#3562) by @szokeasaurusrex
Miscellaneous
sentry_sdk.metrics
(#3512) by @szokeasaurusrexname
parameter tostart_span()
and deprecatedescription
parameter (#3524 & #3525) by @antonpirkeradd_query_source
with modules outside of project root (#3313) by @rominfget_integration
typing (#3550) by @szokeasaurusrexlogger.warn
(#3552) by @sentrivanaexplain_plan
feature. (#3534) by @antonpirkeractions/upload-artifact
tov4
with merge (#3545) by @joshuarliactions/checkout
from4.1.7
to4.2.0
(#3585) by @dependabotConfiguration
📅 Schedule: Branch creation - "after 10pm every weekday,every weekend" in timezone Africa/Lusaka, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.