-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update dependency sentry-sdk to v2.18.0 #296
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/sentry-sdk-2.x-lockfile
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
Update dependency sentry-sdk to v2.10.0
Update dependency sentry-sdk to v2.10.0 - autoclosed
Jul 19, 2024
renovate
bot
changed the title
Update dependency sentry-sdk to v2.10.0 - autoclosed
Update dependency sentry-sdk to v2.10.0
Jul 24, 2024
renovate
bot
force-pushed
the
renovate/sentry-sdk-2.x-lockfile
branch
from
July 24, 2024 09:27
b1e92ac
to
256c37c
Compare
renovate
bot
changed the title
Update dependency sentry-sdk to v2.10.0
Update dependency sentry-sdk to v2.11.0
Jul 24, 2024
renovate
bot
force-pushed
the
renovate/sentry-sdk-2.x-lockfile
branch
from
July 28, 2024 19:08
256c37c
to
d3fb5db
Compare
renovate
bot
changed the title
Update dependency sentry-sdk to v2.11.0
Update dependency sentry-sdk to v2.12.0
Jul 31, 2024
renovate
bot
force-pushed
the
renovate/sentry-sdk-2.x-lockfile
branch
from
July 31, 2024 12:17
d3fb5db
to
aede171
Compare
renovate
bot
force-pushed
the
renovate/sentry-sdk-2.x-lockfile
branch
from
August 13, 2024 16:24
aede171
to
3ff4dfd
Compare
renovate
bot
changed the title
Update dependency sentry-sdk to v2.12.0
Update dependency sentry-sdk to v2.13.0
Aug 13, 2024
renovate
bot
force-pushed
the
renovate/sentry-sdk-2.x-lockfile
branch
from
September 9, 2024 16:35
3ff4dfd
to
df642b2
Compare
renovate
bot
changed the title
Update dependency sentry-sdk to v2.13.0
Update dependency sentry-sdk to v2.14.0
Sep 9, 2024
renovate
bot
changed the title
Update dependency sentry-sdk to v2.14.0
Update dependency sentry-sdk to v2.15.0
Oct 1, 2024
renovate
bot
force-pushed
the
renovate/sentry-sdk-2.x-lockfile
branch
2 times, most recently
from
October 8, 2024 13:41
eee934a
to
cd84bf7
Compare
renovate
bot
changed the title
Update dependency sentry-sdk to v2.15.0
Update dependency sentry-sdk to v2.16.0
Oct 8, 2024
renovate
bot
force-pushed
the
renovate/sentry-sdk-2.x-lockfile
branch
from
October 17, 2024 10:12
cd84bf7
to
f74d5ee
Compare
renovate
bot
changed the title
Update dependency sentry-sdk to v2.16.0
Update dependency sentry-sdk to v2.17.0
Oct 17, 2024
| datasource | package | from | to | | ---------- | ---------- | ------ | ------ | | pypi | sentry-sdk | 2.10.0 | 2.18.0 |
renovate
bot
force-pushed
the
renovate/sentry-sdk-2.x-lockfile
branch
from
November 4, 2024 14:05
f74d5ee
to
1da6f66
Compare
renovate
bot
changed the title
Update dependency sentry-sdk to v2.17.0
Update dependency sentry-sdk to v2.18.0
Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.10.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 @dependabotv2.14.0
Compare Source
Various fixes & improvements
New
SysExitIntegration
(#3401) by @szokeasaurusrexFor more information, see the documentation for the SysExitIntegration.
Add
SENTRY_SPOTLIGHT
env variable support (#3443) by @BYKSupport Strawberry
0.239.2
(#3491) by @szokeasaurusrexAdd separate
pii_denylist
toEventScrubber
and run it always (#3463) by @sl0thentr0pyCelery: Add wrapper for
Celery().send_task
to support behavior asTask.apply_async
(#2377) by @divaltorDjango: SentryWrappingMiddleware.init fails if super() is object (#2466) by @cameron-simpson
Fix data_category for sessions envelope items (#3473) by @sl0thentr0py
Fix non-UTC timestamps (#3461) by @szokeasaurusrex
Remove obsolete object as superclass (#3480) by @sentrivana
Replace custom
TYPE_CHECKING
with stdlibtyping.TYPE_CHECKING
(#3447) by @dev-satoshiRefactor
tracing_utils.py
(#3452) by @rominfExplicitly export symbol in subpackages instead of ignoring (#3400) by @hartungstenio
Better test coverage reports (#3498) by @antonpirker
Fixed config for old coverage versions (#3504) by @antonpirker
Fix AWS Lambda tests (#3495) by @antonpirker
Remove broken Bottle tests (#3505) by @sentrivana
v2.13.0
Compare Source
Various fixes & improvements
New integration: Ray (#2400) (#2444) by @glowskir
Usage: (add the RayIntegration to your
sentry_sdk.init()
call and make sure it is called in the worker processes)For more information, see the documentation for the Ray integration.
New integration: Litestar (#2413) (#3358) by @KellyWalker
Usage: (add the LitestarIntegration to your
sentry_sdk.init()
)For more information, see the documentation for the Litestar integration.
New integration: Dramatiq from @jacobsvante (#3397) by @antonpirker
Usage: (add the DramatiqIntegration to your
sentry_sdk.init()
)For more information, see the documentation for the Dramatiq integration.
New config option: Expose
custom_repr
function that precedessafe_repr
invocation in serializer (#3438) by @sl0thentr0pySee: https://docs.sentry.io/platforms/python/configuration/options/#custom-repr
Profiling: Add client SDK info to profile chunk (#3386) by @Zylphrex
Serialize vars early to avoid living references (#3409) by @sl0thentr0py
Deprecate hub-based
sessions.py
logic (#3419) by @szokeasaurusrexDeprecate
is_auto_session_tracking_enabled
(#3428) by @szokeasaurusrexAdd note to generated yaml files (#3423) by @sentrivana
Slim down PR template (#3382) by @sentrivana
Use new banner in readme (#3390) by @sentrivana
v2.12.0
Compare Source
Various fixes & improvements
push_scope
deprecation warning (#3355) (#3355) by @szokeasaurusrexpush_scope
(#3353, #3354) by @szokeasaurusrexconfigure_scope
(#3348, #3349, #3350, #3351) by @szokeasaurusrexai_track
decorator (#3376) by @czyberadd_attachment
type (#3342) by @szokeasaurusrex0feb234
to6d2c435
(#3369) by @dependabot88273a9
to0feb234
(#3252) by @dependabotv2.11.0
Compare Source
Various fixes & improvements
Add
disabled_integrations
(#3328) by @sentrivanaDisabling individual integrations is now much easier.
Instead of disabling all automatically enabled integrations and specifying the ones
you want to keep, you can now use the new
disabled_integrations
config option to provide a list of integrations to disable:
Do not use the Flask integration even if Flask is installed.
)
Configuration
📅 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 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.