-
Notifications
You must be signed in to change notification settings - Fork 4
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/node to v8 #44
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-sentry-javascript-monorepo
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
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
May 28, 2024 02:17
9438e66
to
7bf8ccc
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 31, 2024 14:54
7bf8ccc
to
328baf5
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
June 12, 2024 11:48
dfe9754
to
544f767
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
June 26, 2024 20:27
5a5e80a
to
7b5653c
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
July 5, 2024 02:28
51f39da
to
a1236e3
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
July 11, 2024 05:48
a87fb41
to
14eb33e
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
July 26, 2024 02:41
5857b0b
to
88153b9
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
August 6, 2024 23:48
e06ce69
to
49ad210
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
August 15, 2024 05:52
cd14a08
to
dfbca53
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
August 28, 2024 02:23
dfbca53
to
a45af83
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
September 10, 2024 20:50
535907f
to
2604ff4
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
September 25, 2024 18:00
327e1e5
to
134d6b5
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 3, 2024 02:21
134d6b5
to
b393a29
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 4, 2024 04:58
b393a29
to
ef1bc52
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 11, 2024 11:30
ef1bc52
to
f7d8edb
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 22, 2024 02:39
f7d8edb
to
9ac7115
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
November 6, 2024 20:29
8eee8b4
to
7d16e02
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
November 19, 2024 20:39
e019105
to
557315c
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
November 28, 2024 02:39
f353f05
to
b50ca41
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 3, 2024 05:50
b50ca41
to
df6f307
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
December 14, 2024 02:04
eb9685b
to
7369130
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 21, 2024 02:52
7369130
to
0fa9015
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
January 9, 2025 12:10
0fa9015
to
9640076
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
January 17, 2025 06:53
9640076
to
382f014
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
January 23, 2025 04:22
382f014
to
84c42dc
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.42.0
->^8.51.0
Release Notes
getsentry/sentry-javascript (@sentry/node)
v8.51.0
Compare Source
Important Changes
feat(v8/node): Add
prismaInstrumentation
option to Prisma integration as escape hatch for all Prisma versions (#15128)This release adds a compatibility API to add support for Prisma version 6.
To capture performance data for Prisma version 6:
Install the
@prisma/instrumentation
package on version 6.Pass a
new PrismaInstrumentation()
instance as exported from@prisma/instrumentation
to theprismaInstrumentation
option:The passed instrumentation instance will override the default instrumentation instance the integration would use, while the
prismaIntegration
will still ensure data compatibility for the various Prisma versions.Remove the
previewFeatures = ["tracing"]
option from the client generator block of your Prisma schema.Other Changes
multiplexedtransport.js
CDN bundle (#15046)fetchProxyScriptNonce
option (#15011)fatal
events should set session as crashed (#15073)Work in this release was contributed by @tjhiggins, and @nwalters512. Thank you for your contributions!
Bundle size 📦
v8.50.0
Compare Source
createMemoryRouter
(#14985)Bundle size 📦
v8.49.0
Compare Source
handled
prop to ErrorBoundary (#14978)require
,__filename
and__dirname
on global object (#14952)Work in this release was contributed by @HHK1 and @mstrokin. Thank you for your contribution!
Bundle size 📦
v8.48.0
Compare Source
Deprecations
feat(v8/core): Deprecate
getDomElement
method (#14799)Deprecates
getDomElement
. There is no replacement.Other changes
continueTrace
implementation in core (#14819)NODE_OPTIONS
is not passed to worker threads (#14825)tagName
when name is not provided toTraceDirective
(#14828)openTelemetrySpanProcessors
option (#14853)Set
as theallRoutes
container. (#14878) (#14884)normalizedRequest
tosamplingContext
(#14903)syncFeedbackIntegration
(#14918)Work in this release was contributed by @arturovt. Thank you for your contribution!
Bundle size 📦
v8.47.0
Compare Source
updateSpanName
helper function (#14736)db.system
in newer Prisma versions (#14772)Work in this release was contributed by @aloisklink and @benjick. Thank you for your contributions!
Bundle size 📦
v8.46.0
Compare Source
Work in this release was contributed by @conor-ob. Thank you for your contribution!
Bundle size 📦
v8.45.1
Compare Source
sendFeedback
promise resolves (#14683)Bundle size 📦
v8.45.0
Compare Source
handled
option tocaptureConsoleIntegration
(#14664)HttpClient
events (#14515)captureMessage
withattachStacktrace: true
as synthetic (#14668)captureMessage
withattatchStackTrace: true
as synthetic (#14670)level
in server runtimecaptureException
(#10587)Work in this release was contributed by @anonrig and @Zih0. Thank you for your contributions!
v8.44.0
Compare Source
Deprecations
feat: Deprecate
autoSessionTracking
(#14640)Deprecates
autoSessionTracking
.To enable session tracking, it is recommended to unset
autoSessionTracking
and ensure that either, in browser environmentsthe
browserSessionIntegration
is added, or in server environments thehttpIntegration
is added.To disable session tracking, it is recommended to unset
autoSessionTracking
and to remove thebrowserSessionIntegration
inbrowser environments, or in server environments configure the
httpIntegration
with thetrackIncomingRequestsAsSessions
option set tofalse
.Other Changes
response
context for http.server spans (#14634)Work in this release was contributed by @robinvw1. Thank you for your contribution!
v8.43.0
Compare Source
Important Changes
feat(nuxt): Add option autoInjectServerSentry (no default import()) (#14553)
Using the dynamic
import()
as the default behavior for initializing the SDK on the server-side did not work for every project.The default behavior of the SDK has been changed, and you now need to use the
--import
flag to initialize Sentry on the server-side to leverage full functionality.Example with
--import
:In case you are not able to use the
--import
flag, you can enable auto-injecting Sentry in thenuxt.config.ts
(comes with limitations):feat(browser): Adds LaunchDarkly and OpenFeature integrations (#14207)
Adds browser SDK integrations for tracking feature flag evaluations through the LaunchDarkly JS SDK and OpenFeature Web SDK:
feat(browser): Add
featureFlagsIntegration
for custom tracking of flag evaluations (#14582)Adds a browser integration to manually track feature flags with an API. Feature flags are attached to subsequent error events:
feat(astro): Add Astro 5 support (#14613)
With this release, the Sentry Astro SDK officially supports Astro 5.
Deprecations
feat(nextjs): Deprecate typedef for
hideSourceMaps
(#14594)The functionality of
hideSourceMaps
was removed in version 8 but was forgotten to be deprecated and removed.It will be completely removed in the next major version.
feat(core): Deprecate APIs around
RequestSession
s (#14566)The APIs around
RequestSession
s are mostly used internally.Going forward the SDK will not expose concepts around
RequestSession
s.Instead, functionality around server-side Release Health will be managed in integrations.
Other Changes
browserSessionIntegration
(#14551)raw_security
envelope types (#14562)disableAnrDetectionForCallback
function (#14359)trackIncomingRequestsAsSessions
option to http integration (#14567)autoInjectServerSentry
(no defaultimport()
) (#14553)^1.29.0
(#14590)1.28.0
(#14547)filename
andmodule
stack frame properties in Node stack parser (#14544)maxSpanWaitDuration
values (#14632)parseSearch
option in TanStack Router instrumentation (#14328)Work in this release was contributed by @lsmurray. Thank you for your contribution!
v8.42.0
Compare Source
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)Bundle size 📦
v8.41.0
Compare Source
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 the@sentry/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)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.