-
Notifications
You must be signed in to change notification settings - Fork 20
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 dependency @sentry/node to v8 #676
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
August 14, 2024 08:09
18c8a89
to
9ac9586
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
August 21, 2024 00:30
9ac9586
to
a74e632
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
August 27, 2024 14:29
a74e632
to
16717b8
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 1, 2024 18:42
16717b8
to
42b3f51
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 1, 2024 19:11
42b3f51
to
79512a2
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 3, 2024 13:10
79512a2
to
177a7cd
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 9, 2024 10:19
177a7cd
to
2e09039
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 10, 2024 15:04
2e09039
to
524eba1
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 23, 2024 11:16
524eba1
to
b92d712
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 25, 2024 10:25
b92d712
to
d3b1ba9
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 27, 2024 13:31
2ed12be
to
4f1fda6
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 2, 2024 17:37
4f1fda6
to
e461b0c
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 11, 2024 17:55
e461b0c
to
ccc11bb
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 12, 2024 12:47
ccc11bb
to
08a238d
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 13, 2024 13:46
08a238d
to
f5897b0
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 16, 2024 15:42
f5897b0
to
7efe89e
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 17, 2024 14:36
7efe89e
to
6a85d18
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 21, 2024 14:28
6a85d18
to
a0e33e7
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
January 6, 2025 05:58
a0e33e7
to
ae941b9
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
January 8, 2025 13:32
ae941b9
to
05c4fa2
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
January 15, 2025 10:58
05c4fa2
to
a10972f
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
January 15, 2025 16:15
a10972f
to
0f1614d
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
January 23, 2025 07:29
0f1614d
to
a36a8e4
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
January 28, 2025 17:29
a36a8e4
to
efd604e
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.118.0
->^8.52.0
Release Notes
getsentry/sentry-javascript (@sentry/node)
v8.52.0
Compare Source
Important Changes
withSentry
wrapper for SolidStart config (#15135)To enable the SolidStart SDK, wrap your SolidStart Config with
withSentry
. ThesentrySolidStartVite
plugin is now automaticallyadded by
withSentry
and you can pass the Sentry build-time options like this:With the
withSentry
wrapper, the Sentry server config should not be added to thepublic
directory anymore.Add the Sentry server config in
src/instrument.server.ts
. Then, the server config will be placed inside the server build output asinstrument.server.mjs
.Now, there are two options to set up the SDK:
--import
CLI flag to the start command like this (path depends on your server setup):node --import ./.output/server/instrument.server.mjs .output/server/index.mjs
autoInjectServerSentry: 'top-level-import'
and the Sentry config will be imported at the top of the server entry (comes with tracing limitations)Other Changes
Bun.serve
survives a server reload (#15157)module
intoloadModule
(#15139) (#15166)Work in this release was contributed by @jahands, @jrandolf, and @nathankleyn. Thank you for your contributions!
Bundle size 📦
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 📦
Configuration
📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.