-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
chore(deps): update JavaScript Sibling SDKs to v8.42.0 #730
Open
github-actions
wants to merge
5
commits into
main
Choose a base branch
from
deps/scripts/update-javascript-siblings.sh
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.
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
github-actions
bot
added
the
dependencies
Pull requests that update a dependency file
label
Sep 12, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
2 times, most recently
from
September 12, 2024 12:07
23e109c
to
41aa469
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.30.0
chore(deps): update JavaScript Sibling SDKs to v8.31.0
Sep 23, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
5 times, most recently
from
September 26, 2024 03:07
e852e17
to
9855685
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.31.0
chore(deps): update JavaScript Sibling SDKs to v8.32.0
Sep 26, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
2 times, most recently
from
October 3, 2024 03:07
22d8c96
to
f91d739
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.32.0
chore(deps): update JavaScript Sibling SDKs to v8.33.0
Oct 3, 2024
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.33.0
chore(deps): update JavaScript Sibling SDKs to v8.33.1
Oct 4, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
from
October 4, 2024 03:07
f91d739
to
9d3e381
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.33.1
chore(deps): update JavaScript Sibling SDKs to v8.34.0
Oct 18, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
from
October 18, 2024 03:08
9d3e381
to
37661d1
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.34.0
chore(deps): update JavaScript Sibling SDKs to v8.35.0
Oct 22, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
3 times, most recently
from
October 24, 2024 14:32
a836ba8
to
79aba92
Compare
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
from
November 1, 2024 03:14
79aba92
to
fb8428d
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.35.0
chore(deps): update JavaScript Sibling SDKs to v8.36.0
Nov 1, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
2 times, most recently
from
November 5, 2024 12:45
4c375b1
to
36b0c57
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.36.0
chore(deps): update JavaScript Sibling SDKs to v8.37.1
Nov 6, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
3 times, most recently
from
November 12, 2024 00:08
c6128ed
to
c27d980
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.37.1
chore(deps): update JavaScript Sibling SDKs to v8.38.0
Nov 13, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
6 times, most recently
from
November 18, 2024 12:43
055eae3
to
fbd8203
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.38.0
chore(deps): update JavaScript Sibling SDKs to v8.39.0
Nov 19, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
3 times, most recently
from
November 19, 2024 16:21
98cb152
to
bd2c5d6
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.39.0
chore(deps): update JavaScript Sibling SDKs to v8.40.0
Nov 23, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
from
November 23, 2024 03:10
bd2c5d6
to
d375443
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.40.0
chore(deps): update JavaScript Sibling SDKs to v8.41.0
Nov 28, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
from
November 28, 2024 03:15
d375443
to
db0d712
Compare
github-actions
bot
changed the title
chore(deps): update JavaScript Sibling SDKs to v8.41.0
chore(deps): update JavaScript Sibling SDKs to v8.42.0
Dec 3, 2024
github-actions
bot
force-pushed
the
deps/scripts/update-javascript-siblings.sh
branch
from
December 3, 2024 03:17
db0d712
to
f077a1b
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Bumps scripts/update-javascript-siblings.sh from 8.37.1 to 8.42.0.
Auto-generated by a dependency updater.
Changelog
8.42.0
Important Changes
feat(react): React Router v7 support (library) (#14513)
This release adds support for React Router v7 (library mode).
Check out the docs on how to set up the integration: Sentry React Router v7 Integration Docs
Deprecations
feat: Warn about source-map generation (#14533)
In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application.
Currently, the implementation varies a lot between different SDKs and can be difficult to understand.
Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off.
Additionally, if we end up enabling source maps, we will emit a log message that we did so.
With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.
feat(nuxt): Deprecate
tracingOptions
in favor ofvueIntegration
(#14530)Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:
Sentry.init()
tracingOptions
inSentry.init()
For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported
vueIntegration()
and itstracingOptions
option to configure tracing options in the Nuxt SDK:Other Changes
web-vitals
to v4.2.4 (#14439)vueIntegration
(#14526)8.41.0
Important Changes
meta(nuxt): Require minimum Nuxt v3.7.0 (#14473)
We formalized that the Nuxt SDK is at minimum compatible with Nuxt version 3.7.0 and above.
Additionally, the SDK requires the implicit
nitropack
dependency to satisfy version^2.10.0
andofetch
to satisfy^1.4.0
.It is recommended to check your lock-files and manually upgrade these dependencies if they don't match the version ranges.
Deprecations
We are deprecating a few APIs which will be removed in the next major.
The following deprecations will potentially affect you:
feat(core): Update & deprecate
undefined
option handling (#14450)In the next major version we will change how passing
undefined
totracesSampleRate
/tracesSampler
/enableTracing
will behave.Currently, doing the following:
Will result in tracing being enabled (although no spans will be generated) because the
tracesSampleRate
key is present in the options object.In the next major version, this behavior will be changed so that passing
undefined
(or rather having atracesSampleRate
key) will result in tracing being disabled, the same as not passing the option at all.If you are currently relying on
undefined
being passed, and and thus have tracing enabled, it is recommended to update your config to set e.g.tracesSampleRate: 0
instead, which will also enable tracing in v9.The same applies to
tracesSampler
andenableTracing
.feat(core): Log warnings when returning
null
inbeforeSendSpan
(#14433)Currently, the
beforeSendSpan
option inSentry.init()
allows you to drop individual spans from a trace by returningnull
from the hook.Since this API lends itself to creating "gaps" inside traces, we decided to change how this API will work in the next major version.
With the next major version the
beforeSendSpan
API can only be used to mutate spans, but no longer to drop them.With this release the SDK will warn you if you are using this API to drop spans.
Instead, it is recommended to configure instrumentation (i.e. integrations) directly to control what spans are created.
Additionally, with the next major version, root spans will also be passed to
beforeSendSpan
.feat(utils): Deprecate
sentry/utils
(#14431)With the next major version the
sentry/utils
package will be merged into thesentry/core
package.It is therefore no longer recommended to use the
sentry/utils
package.feat(vue): Deprecate configuring Vue tracing options anywhere else other than through the
vueIntegration
'stracingOptions
option (#14385)Currently it is possible to configure tracing options in various places in the Sentry Vue SDK:
Sentry.init()
tracingOptions
inSentry.init()
vueIntegration()
optionstracingOptions
in thevueIntegration()
optionsBecause this is a bit messy and confusing to document, the only recommended way to configure tracing options going forward is through the
tracingOptions
in thevueIntegration()
.The other means of configuration will be removed in the next major version of the SDK.
feat: Deprecate
registerEsmLoaderHooks.include
andregisterEsmLoaderHooks.exclude
(#14486)Currently it is possible to define
registerEsmLoaderHooks.include
andregisterEsmLoaderHooks.exclude
options inSentry.init()
to only apply ESM loader hooks to a subset of modules.This API served as an escape hatch in case certain modules are incompatible with ESM loader hooks.
Since this API was introduced, a way was found to only wrap modules that there exists instrumentation for (meaning a vetted list).
To only wrap modules that have instrumentation, it is recommended to instead set
registerEsmLoaderHooks.onlyIncludeInstrumentedModules
totrue
.Note that
onlyIncludeInstrumentedModules: true
will become the default behavior in the next major version and theregisterEsmLoaderHooks
will no longer accept fine-grained options.The following deprecations will most likely not affect you unless you are building an SDK yourself:
arrayify
(#14405)flatten
(#14454)urlEncode
(#14406)validSeverityLevels
(#14407)getNumberOfUrlSegments
(#14458)memoBuilder
,BAGGAGE_HEADER_NAME
, andmakeFifoCache
(#14434)addRequestDataToEvent
andextractRequestData
(#14430)Other Changes
sentry-trace
,baggage
and DSC handling (#14364)openTelemetryInstrumentations
option (#14484)NEXT_REDIRECT
from browser (#14440)Work in this release was contributed by NEKOYASAN and fmorett. Thank you for your contributions!
8.40.0
Important Changes
feat(angular): Support Angular 19 (#14398)
The
sentry/angular
SDK can now be used with Angular 19. If you're upgrading to the new Angular version, you might want to migrate from the now deprecatedAPP_INITIALIZER
token toprovideAppInitializer
.In this case, change the Sentry
TraceService
initialization inapp.config.ts
:feat(core): Deprecate
debugIntegration
andsessionTimingIntegration
(#14363)The
debugIntegration
was deprecated and will be removed in the next major version of the SDK.To log outgoing events, use Hook Options (
beforeSend
,beforeSendTransaction
, ...).The
sessionTimingIntegration
was deprecated and will be removed in the next major version of the SDK.To capture session durations alongside events, use Context (
Sentry.setContext()
).feat(nestjs): Deprecate
WithSentry
in favor ofSentryExceptionCaptured
(#14323)The
WithSentry
decorator was deprecated. UseSentryExceptionCaptured
instead. This is a simple renaming and functionality stays identical.feat(nestjs): Deprecate
SentryTracingInterceptor
,SentryService
,SentryGlobalGenericFilter
,SentryGlobalGraphQLFilter
(#14371)The
SentryTracingInterceptor
was deprecated. If you are usingsentry/nestjs
you can safely remove any references to theSentryTracingInterceptor
. If you are using another package migrate tosentry/nestjs
and remove theSentryTracingInterceptor
afterwards.The
SentryService
was deprecated and its functionality was added toSentry.init
. If you are usingsentry/nestjs
you can safely remove any references to theSentryService
. If you are using another package migrate tosentry/nestjs
and remove theSentryService
afterwards.The
SentryGlobalGenericFilter
was deprecated. Use theSentryGlobalFilter
instead which is a drop-in replacement.The
SentryGlobalGraphQLFilter
was deprecated. Use theSentryGlobalFilter
instead which is a drop-in replacement.feat(node): Deprecate
nestIntegration
andsetupNestErrorHandler
in favor of usingsentry/nestjs
(#14374)The
nestIntegration
andsetupNestErrorHandler
functions fromsentry/node
were deprecated and will be removed in the next major version of the SDK. If you're usingsentry/node
in a NestJS application, we recommend switching to our new dedicatedsentry/nestjs
package.Other Changes
normalizedRequest
onsdkProcessingMetadata
is merged (#14315)sentry/utils
intosentry/core
(#14382)__self
and__source
attributes on feedback nodes (#14356)8.39.0
Important Changes
The
sentry/nestjs
SDK will now capture performance data for NestJS Events (nestjs/event-emitter
)Other Changes
SentryExceptionCaptured
forWithSentry
(#14322)SentryService
behaviour intosentry/nestjs
SDKinit()
(#14321)SentryGlobalFilter
(#14320)childProcessIntegration
forprocessThreadBreadcrumbIntegration
and deprecate it (#14334)_sentryModuleMetadata
is not mangled (#14344)sentry.source
attribute tocustom
when callingspan.updateName
onSentrySpan
(#14251)Request
type in favor ofRequestEventData
(#14317)transaction
inrequestDataIntegration
(#14306)8.38.0
knex
integration (#13526)tedious
integration (#13486)debug_meta
with ANR events (#14203)Work in this release was contributed by grahamhency, Zen-cronic, gilisho and phuctm97. Thank you for your contributions!