Repository navigation
fix(deps): update dependency @sentry/node to v11 - #676
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
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 12, 2024 17:43
f9a0225 to
b9dc11e
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 19, 2024 17:22
b9dc11e to
931e34d
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 22, 2024 14:26
931e34d to
2ed12be
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
This branch was successfully deployed
This file contains hidden or 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
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
^7.118.0→^11.9.0Release Notes
getsentry/sentry-javascript (@sentry/node)
v11.9.0Compare Source
Important Changes
feat: Rename
diagnostic_channel, fetch and gRPC span origins (#25601)Some span origins changed their names to match the other v11 origins:
auto.graphql.diagnostic_channelis nowauto.graphql.graphql.auto.db.redis.diagnostic_channel,auto.db.mysql2.diagnostic_channelandauto.db.mongoose.diagnostic_channelnow end in.native_channel.auto.http.wintercg_fetchis nowauto.http.fetch, as on Bun, Deno and Cloudflare.auto.grpc.serverlessis nowauto.grpc.google_cloud.If you have
ignoreSpansrules, queries or alerts on the old origins, change them to use the new origins.feat(deno): Add incoming request options to
denoServeIntegration(#25493)denoServeIntegrationnow acceptsignoreRequestBody,ignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreatedandonSpanEnd, with the same meaning as indenoHttpIntegration. The callbacks receive the webRequest.ignoreStaticAssetsdefaults totrue, soDeno.serveno longer creates spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, setdenoServeIntegration({ ignoreStaticAssets: false }).Deno.servespans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled.feat(deno): Record request sessions for
Deno.serve(#25496)denoServeIntegrationnow records a request session for each incoming request, asdenoHttpIntegrationdoes fornode:http. This gives release health and crash-free rates forDeno.serveapps. Sessions are sent only when areleaseis set. To turn them off, setdenoServeIntegration({ sessions: false }).sessionFlushingDelayMSsets how long the SDK waits before it sends the session aggregate.feat(deno): Register channel injection hooks from
init()(#25546)Sentry.init()in@sentry/denonow registers the diagnostics-channel injection hooks, as@sentry/nodedoes. The channel integrations now record spans without--preload=npm:@sentry/deno/import, for modules that you import afterinit(). To also instrument modules that load beforeinit(), such as static imports in your entry module, keep the preload. Withdebug: true, the SDK logs a warning when no injection is active.On Node.js, tracing-hooks messages now show with
debug: trueinstead of withDEBUG=@apm-js-collab/*.feat(nextjs): Add a tunnel route handler that sends only the event payload to Sentry (#25456)
The
tunnelRouteoption can now send events through a route handler in your app. The handler forwards only the event payload to Sentry, and no request headers. To use it, add this file next to yourtunnelRouteoption:The handler accepts events for the DSN of your server SDK. To accept other DSNs, use
createSentryTunnelRoute({ allowedDsns })from the same import. Without the file, the tunnel route works as before.Also, the server no longer sends spans of tunnel requests when span streaming is on, because these spans only show the SDK's own traffic.
feat(nextjs): Never emit trace meta tags from a prerender (#25141)
Pageloads of apps with
cacheComponentsenabled are connected to their server request again. Pages that Next.js prerenders no longer carry trace information, so a cached page can no longer connect visitors to a request that was not theirs. This also applies to ISR pages. The pageload waits for the trace information when it arrives with the part of the page that streams in after a cached shell.If you set up OpenTelemetry yourself and register
SentryPropagator, registerNextSentryPropagatorinstead and pass your tracer provider tomarkPrerendersOnTracerProvider, so that your prerendered pages carry no trace information either.feat(nextjs): Send tunnel route requests with
credentials: 'omit'(#25509)With
tunnelRouteand no tunnel route handler,@sentry/nextjsnow sends events from the browser withcredentials: 'omit', because the tunnel route does not need cookies.If a layer in front of your app checks cookies before it lets requests through (for example Vercel Deployment Protection), you can send them again in your browser
Sentry.initcall:feat(nitro): Report a single
http.serverspan per request (#25295)A Nitro request now creates only one
http.serverspan. The nestedhttp.serverspans with the originsauto.http.nitro.srvxandauto.http.nitro.h3are removed. h3 route handlers now get ahandlerspan, and middleware spans are direct children of thehttp.serverspan. If you have queries or alerts on the removed spans, change them to use thehttp.serverspan or thehandlerspan.fix: Use
auto.http.http_serverorigin for allnode:httpserver spans (#25604)On Bun and Deno,
node:httpserver spans now have the originauto.http.http_serverinstead ofauto.http.server, as on Node.js. On Node.js, nothing changes.Bun.servespans keepauto.http.bun.serveandDeno.servespans keepauto.http.deno. If you haveignoreSpansorbeforeSendSpanrules, queries or alerts onauto.http.server, change them to useauto.http.http_server.Other Changes
LoaderSentrytype export (#25357)isStreamingResponseoption and detect streamed RSC responses (#24932)dataCollection.mcpoption (#25553)use cachehits to their fill across instances (#25448)nitroIntegration(#25349)execute_toolspans for Anthropic'sbeta.messages.toolRunner()(#25320)@sentry/cloudflare/viteon Cloudflare Workers (#25347)function.awsspan when a callback-style handler calls back (#25543)globalThisbeforeglobalin the injected snippet (#25365)trace_metricdata category for metrics rate limits and client reports (#25606)@opentelemetry/api1.9 again (#25684)node:httpserver instrumentation (#25592)error.causeis not an Error (#25542)Internal Changes
@types/nodeto 20 (#25501).binscripts (#25635)Work in this release was contributed by @4ktLuffy, @adityareddy-dev, @dasilvaluis, @faizansaiyed123, @jpdefo, @Jxxunnn, @mikamikasuki, @philipatkinson, @rubas, and @Shubham-Padkonde. Thank you for your contributions!
feat(bun): Add incoming request options and request sessions to
bunServerIntegrationbunServerIntegrationnow accepts the same options asdenoServeIntegration:ignoreRequestBody,ignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreated,onSpanEnd,sessionsandsessionFlushingDelayMS. The callbacks receive the webRequest.Bun.servenow records a request session for each incoming request. Sessions are sent only when areleaseis set. To turn them off, setbunServerIntegration({ sessions: false }).ignoreStaticAssetsdefaults totrue, soBun.serveno longer creates spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, setbunServerIntegration({ ignoreStaticAssets: false }).Bun.servespans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. Errors thrown forOPTIONSandHEADrequests are now captured.feat(node): Add
onSpanEndtohttpIntegrationhttpIntegrationandhttpServerSpansIntegrationnow acceptonSpanEnd, a hook that runs when the response for an incoming request finishes, before its span ends. Use it to change the span based on the response. Deno and Bun already have this option.feat(bun): Inject debug IDs and upload source maps in
sentryBunPlugin(#25670)sentryBunPluginfrom@sentry/bun/pluginnow accepts the same options assentryEsbuildPlugin(org,project,authToken,release,sourcemaps, ...). WhenBun.buildwrites source maps tooutdir, the plugin injects the debug ID that Bun writes into each bundle, injects the release, and uploads the source maps at the end of the build. You no longer need to runsentry sourcemap injectandsentry sourcemap uploadafter the build.Like the other bundler plugins,
sentryBunPluginnow sends build telemetry and injects the release it detects (for example, from git). To turn off telemetry, settelemetry: false.v11.8.0Compare Source
Important Changes
feat(bundler-plugins): Release
@sentry/webpack-plugin,@sentry/vite-plugin,@sentry/rollup-pluginand@sentry/esbuild-pluginfrom the SDK repository (#25095)The four standalone bundler plugins now release together with the SDK, so their version jumps from 5.4.1 to the SDK version. Each package re-exports the matching
@sentry/bundler-pluginsentry point, which we recommend for new projects. The plugin options do not change, but the update brings these breaking changes:@sentry/webpack-pluginrequires webpack 5.1 or higher. The@sentry/webpack-plugin/webpack5entry point still works and exports the same plugin as@sentry/webpack-plugin.sentryCLI SDK instead of@sentry/cli. Sentry self-hosted 26.4.2 or higher is supported. Lower versions may continue to work.VERCEL_TARGET_ENV(production,previewor a custom name) as their environment, instead ofvercel-productionorvercel-preview. To keep the old value, setrelease.deploy.env.feat(server-utils): Instrument the OpenAI decisions API as
gen_ai.decidespans (#25285)OpenAI
decisions.createcalls now creategen_ai.decidespans.Other Changes
urlQueryParamsto the Referer header (#25324)mainis a package (#25343)output(#25312)sveltekit.endpointspan (#25376)Internal Changes
Work in this release was contributed by @kunal649 and @mketiku. Thank you for your contributions!
v11.7.0Compare Source
Important Changes
feat(cloudflare): Add opt-in cron monitoring for Cron Triggers (#25014)
The new
cronTriggersIntegrationsends check-ins for Cron Triggers. Each check-in includes the schedule fromcontroller.cron, so Sentry creates the monitor on the first run. The integration is opt-in, because monitors are billed.Cron Triggers have no names, so map each cron expression of your wrangler config to a monitor slug. With the Sentry Cloudflare Vite plugin, add the integration to
src/instrument.server.ts:The
monitorSlugfunction can also return monitor settings, for example{ monitorSlug: 'daily-report', maxRuntime: 30 }, orundefinedto send no check-ins for a trigger. WithoutmonitorSlug, the SDK derives the slug from the cron expression. If you deploy withwranglerdirectly, pass the same integration toSentry.withSentry.feat(node): Add neonIntegration for @neondatabase/serverless (#25164, #25176)
The new
neonIntegrationcreatesdbspans for queries of the@neondatabase/serverlessdriver: for the WebSocketClientandPool, and for the HTTPneon()function. This includes theneon-httpandneon-serverlessadapters of Drizzle. The integration is on by default when tracing is enabled.feat(node): Stop sending the process session once request sessions are tracked (#24915)
Node servers sent release health data two times: as request session aggregates, and as the process session of
processSessionIntegration. An error in a request also marked the process session as errored, so the SDK counted the error two times. Now the SDK drops the process session when it tracks the first request session. Scripts, CLIs and workers that do not serve requests keep the process session, and so do servers withhttpServerIntegration({ sessions: false }). This changes the release health numbers of Node servers, because they no longer send the errored or crashed update of the process session.feat(server-utils): Record decide calls as
gen_ai.decidespans (#25270, #25272, #25274, #25281)Vercel AI
experimental_decidecalls, Mastra classifier evaluations, TypeSafe and LangChain Jev calls, and Workers AI calls to TypeSafe Jev and Cloudflare Clef models now createdecide <model>spans with the opgen_ai.decide. Before, these spans had the opgen_ai.evaluate, which is now deprecated in the Sentry conventions. If you usegen_ai.evaluatein queries, alerts or dashboards, change it togen_ai.decide.fix(browser): Apply
urlQueryParamsto more URLs (#25262, #25289)The
dataCollection.urlQueryParamsoption now also filters the query parameters of these URLs:event.request.urlbrowser.*andresource.*span names withtraceLifecycle: 'static'lcp.urlandbrowser.web_vital.lcp.urlui.element.urlattribute ofelementTimingIntegrationBefore this fix, these URLs could send sensitive query values, for example
?jwt=..., to Sentry.fix(nextjs): Apply top-level
bundleSizeOptimizationsto webpack and Turbopack builds (#24818)The top-level
bundleSizeOptimizationsoption now removes unused SDK code in webpack and in Turbopack builds. Before, the tree-shaking options had no effect on Turbopack. Thewebpack.treeshakeoption is deprecated. It still works, but when you set both options,bundleSizeOptimizationstakes precedence.Other Changes
@nuxt/kit4.6 (#25138)spanclient report outcomes when discarding transactions (#25006)@sentry/server-runtime-injectionexternal on Nitro v3 (#24901)Internal Changes
@sentry/conventionsto 0.27.0 (#25264)conditionalTestwith asupportshelper (#25202)NODE_VERSIONandRUNTIMEfrom the test utils (#25292)nuxt/serverin the nuxt-5 E2E app (#25232)Work in this release was contributed by @Philip-Nwabuwa and @4ktLuffy. Thank you for your contributions!
Bundle size 📦
Configuration
📅 Schedule: (UTC)
🚦 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.