-
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
fix(deps): update sentry-javascript monorepo to v8 (major) #172
Open
renovate
wants to merge
1
commit into
saga
Choose a base branch
from
renovate/major-sentry-javascript-monorepo
base: saga
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
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 16, 2024 21:12
fa524ad
to
7573344
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 17, 2024 04:54
7573344
to
37345f9
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 17, 2024 21:52
37345f9
to
63a9ca8
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 22, 2024 18:27
63a9ca8
to
b211bd5
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 23, 2024 19:44
b211bd5
to
5863b04
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 26, 2024 01:36
5863b04
to
419c238
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 27, 2024 19:54
419c238
to
d7dbc2f
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 29, 2024 16:37
d7dbc2f
to
60e3235
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
June 4, 2024 00:42
60e3235
to
ddf0ab1
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
June 4, 2024 22:23
ddf0ab1
to
4eba19f
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
June 7, 2024 09:21
4eba19f
to
1c20bfb
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
June 10, 2024 18:59
1c20bfb
to
8856d85
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
June 11, 2024 16:22
8856d85
to
d4e141b
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
June 12, 2024 10:54
d4e141b
to
fb1b77c
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 25, 2024 11:11
2dbf4f5
to
2389746
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 2, 2024 16:46
2389746
to
1411cec
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 3, 2024 15:25
1411cec
to
2f47a4b
Compare
renovate
bot
changed the title
fix(deps): update sentry-javascript monorepo to v8 (major)
fix(deps): update dependency @sentry/react to v8
Oct 3, 2024
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 4, 2024 15:01
2f47a4b
to
936d035
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 4, 2024 22:31
936d035
to
0218e44
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8
fix(deps): update sentry-javascript monorepo to v8 (major)
Oct 4, 2024
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 10, 2024 19:45
0218e44
to
0b03a4c
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 21, 2024 14:35
0b03a4c
to
d71f469
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 31, 2024 11:42
d71f469
to
c978027
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 5, 2024 17:43
c978027
to
5555e0d
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 12, 2024 17:39
5555e0d
to
9508938
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 13, 2024 21:17
9508938
to
b638bf6
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 19, 2024 17:19
b638bf6
to
dfd04d6
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 22, 2024 14:29
dfd04d6
to
96069d2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
This PR contains the following updates:
7.120.0
->8.40.0
7.120.0
->8.40.0
Release Notes
getsentry/sentry-javascript (@sentry/browser)
v8.40.0
Compare Source
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 of@SentryExceptionCaptured
(#14323)The
@WithSentry
decorator was deprecated. Use@SentryExceptionCaptured
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 using@sentry/nestjs
you can safely remove any references to theSentryTracingInterceptor
. If you are using another package migrate to@sentry/nestjs
and remove theSentryTracingInterceptor
afterwards.The
SentryService
was deprecated and its functionality was added toSentry.init
. If you are using@sentry/nestjs
you can safely remove any references to theSentryService
. If you are using another package migrate to@sentry/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 using@sentry/nestjs
(#14374)The
nestIntegration
andsetupNestErrorHandler
functions from@sentry/node
were deprecated and will be removed in the next major version of the SDK. If you're using@sentry/node
in a NestJS application, we recommend switching to our new dedicated@sentry/nestjs
package.Other Changes
normalizedRequest
onsdkProcessingMetadata
is merged (#14315)@sentry/utils
into@sentry/core
(#14382)__self
and__source
attributes on feedback nodes (#14356)Bundle size 📦
v8.39.0
Compare Source
Important Changes
The
@sentry/nestjs
SDK will now capture performance data for NestJS Events (@nestjs/event-emitter
)Other Changes
@SentryExceptionCaptured
for@WithSentry
(#14322)SentryService
behaviour into@sentry/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)Bundle size 📦
v8.38.0
Compare Source
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!
v8.37.1
Compare Source
v8.37.0
Compare Source
Important Changes
piniaIntegration
(#14138)The Nuxt SDK now allows you to track Pinia state for captured errors. To enable the Pinia plugin, add the
piniaIntegration
to your client config:The Sentry Metrics beta has ended in favour of revisiting metrics in another form at a later date.
This new approach will include different APIs, making the current metrics API unnecessary. This release
deprecates the metrics API with the plan to remove in the next SDK major version. If you currently use the
metrics API in your code, you can safely continue to do so but sent data will no longer be processed by Sentry.
Learn more about the end of the Metrics beta.
Other Changes
http.response_delivery_type
attribute to resource spans (#14056)skipBrowserExtensionCheck
escape hatch option (#14147)asyncFunctionReExports
to define re-exported server functions (#14104)piniaIntegration
(#14138)maybeInstrument
(#14140)modulesIntegration
does not crash esm apps (#14169)Work in this release was contributed by @rexxars. Thank you for your contribution!
v8.36.0
Compare Source
Important Changes
The Nuxt SDK now allows you to track Pinia state for captured errors. To enable the Pinia plugin, set the
trackPinia
option totrue
in your client config:Read more about the Pinia plugin in the Sentry Pinia Documentation.
With this release, the Sentry Next.js, and Cloudflare SDKs will now capture performance data based on OpenTelemetry.
Some exceptions apply in cases where Next.js captures inaccurate data itself.
NOTE: You may experience minor differences in transaction names in Sentry.
Most importantly transactions for serverside pages router invocations will now be named
GET /[param]/my/route
instead of/[param]/my/route
.This means that those transactions are now better aligned with the OpenTelemetry semantic conventions.
Other Changes
child_process
andworker_thread
(#13896).mjs
entry files in rollup (#14060)onError
callback (#14002)v8.35.0
Compare Source
v8.34.0
Compare Source
Important Changes
Relevant for users of the
@sentry/nextjs
package: If you have previously configured aSENTRY_IGNORE_API_RESOLUTION_ERROR
environment variable, it is now safe to unset it.Other Changes
getReplay
in replay CDN bundles(#13881)
(#13914)
globalThis
(#13788)
requestAsyncStorageShim.js
template file(#13928)
(#13920)
_not-found
spans for all HTTP methods(#13906)
(#13929)
(#13769)
dataloader
instrumentation from default integrations(#13873)
(#13909)
replay_id
is removed from frozen DSC when stopped(#13893)
sendBufferedReplayOrFlush
to prevent cycles(#13900)
(#13231)
wrapServerRouteWithSentry
to respect ParamMatchers(#13390)
(#13787) (#13854)
(#13905)
vercelWaitUntil
to utils (#13891)Work in this release was contributed by @trzeciak, @gurpreetatwal, @ykzts and @lizhiyao. Thank you for your
contributions!
Bundle size 📦
v8.33.1
Compare Source
(#13809)
Work in this release was contributed by @soapproject. Thank you for your contribution!
v8.33.0
Compare Source
Important Changes
headers()
,params
,searchParams
)(#13828)
Adds support for new dynamic Next.js APIs.
lru-memoizer
instrumentation(#13796)
Adds integration for lru-memoizer using @opentelemetry/instrumentation-lru-memoizer.
unstable_sentryBundlerPluginOptions
to module options(#13811)
Allows passing other options from the bundler plugins (vite and rollup) to Nuxt module options.
Other Changes
wrap()
only returns functions(#13838)
(#13831)
getTraceData
andgetTraceMetaTags
if SDK is disabled(#13760)
(#13800)
(#13815)
(#13812)
(#13826)
Work in this release was contributed by @joshuajaco. Thank you for your contribution!
Bundle size 📦
v8.32.0
Compare Source
Important Changes
(#13527)
Moves the description of navigation related browser spans into the op, e.g. browser - cache -> browser.cache and sets
the description to the performanceEntry objects' names (in this context it is the URL of the page).
feat(node): Add amqplibIntegration (#13714)
feat(nestjs): Add
SentryGlobalGenericFilter
and allow specifying application ref in global filter(#13673)
Adds a
SentryGlobalGenericFilter
that filters both graphql and http exceptions depending on the context.(#13711)
Sets log levels in breadcrumbs for 5xx to error and 4xx to warning.
Other Changes
sampled
flag from dynamic sampling context in Tracing without Performance mode(#13753)
(#13765)
(#13748)
Work in this release was contributed by @Zen-cronic and @Sjoertjuh. Thank you for your contributions!
v8.31.0
Compare Source
Important Changes
dataloader
integration (#13664)This release adds a new integration for the
dataloader
package. The NodeSDK (and all SDKs that depend on it) will now automatically instrument
dataloader
instances. You can also add itmanually:
Other Changes
activationStart
timestamp to pageload span (#13658)deleteSourcemapsAfterUpload
(#13610)http.server.prefetch
op (#13600)disableInstrumentationWarnings
option (#13693)experimental_basicServerTracing
option to Nuxt module (#13643)onError
callback + other small improvements to debugging (#13721)consoleSandbox
(#13690)lazyLoadIntegration
script parent element lookup (#13717)SentryTraced
functions (#13684)Propagator.inject
(#13381)Work in this release was contributed by @KyGuy2002, @artzhookov, and @julianCast. Thank you for your contributions!
v8.30.0
Compare Source
Important Changes
kafkajs
integration (#13528)This release adds a new integration that instruments
kafkajs
library with spans and traces. This integration isautomatically enabled by default, but can be included with the
Sentry.kafkaIntegration()
import.Other Changes
@opentelemetry/instrumentation-undici
for fetch tracing (#13485)trackComponents
list matches components with or without<>
(#13543)Work in this release was contributed by @Zen-cronic and @odanado. Thank you for your contributions!
v8.29.0
Compare Source
Important Changes
This release marks the beta releases of the
@sentry/solid
and@sentry/solidstart
Sentry SDKs. For details on how touse them, check out the
Sentry Solid SDK README and the
Sentry SolidStart SDK README
respectively. Please reach out on GitHub if you have
any feedback or concerns.
Adds the SDK option to only wrap ES modules with
import-in-the-middle
that specifically need to be instrumented.All internal OpenTelemetry instrumentation was updated to their latest version. This adds support for Mongoose v7 and v8
and fixes various bugs related to ESM mode.
Other Changes
generic-pool
integration (#13465)browserTracingIntegration
by default (#13561)sentrySolidStartVite
plugin to simplify source maps upload (#13493)context.waitUntil
call in request handler (#13549)generic-pool
span origins with underscores (#13579)Work in this release was contributed by @Zen-cronic. Thank you for your contribution!
v8.28.0
Compare Source
Important Changes
This release contains the beta version of
@sentry/nestjs
! For details on how to use it, check out theREADME. Any feedback/bug reports
are greatly appreciated, please reach out on GitHub.
This release fixes a bug in the
@sentry/browser
package and all SDKs depending on this package (e.g.@sentry/react
or
@sentry/nextjs
) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDKpreviously incorrectly processed the original values as they were reported from the browser. When updating your SDK to
this version, you might experience an increase in LCP, FCP and FP values, which potentially leads to a decrease in your
performance score in the Web Vitals Insights module in Sentry. This is because the previously reported values were
smaller than the actually measured val
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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.