Repository navigation
chore(deps): update non-major dependencies - #557
Merged
Merged
Conversation
Contributor
Author
|
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.16.0→7.16.27.16.0→7.16.20.5.10→0.5.130.5.146.0.0→6.0.22.7.1→v2.9.011.8.0→11.10.011.8.0→11.10.011.8.0→11.10.05.104.4→5.105.05.105.3(+2)1.170.45→1.170.461.169.3→1.169.41.168.47→1.168.4826.6.5→26.6.69.31.0→9.32.01.7.10→1.7.141.7.151.59.0→1.63.01.66.0(+2)7.90.0→7.91.04.14.5→4.15.14.17.0(+4)8.71.2→8.72.18.3.4→8.3.55.0.15→5.0.16🔡 If you wish to disable git hash updates, add
":disableDigestUpdates"to the extends array in your config.Release Notes
DataDog/browser-sdk (@datadog/browser-logs)
v7.16.2Compare Source
Public Changes:
Internal Changes:
v7.16.1Compare Source
Public Changes:
<slot>name attribute in session replay (#5141)Internal Changes:
electric-sql/pglite (@electric-sql/pglite)
v0.5.13Compare Source
Patch Changes
c7dc39e:close()now waits for queries, execs and transactions that were issued before it, so they complete instead of failing withCannot read properties of undefinedafter teardown.8364675: Added support for node-postgres through createPgConfig()a4cfd4d: Added MemfsFrontendFS which allows other filesystems be implemented on top of a MEMFS. Example: added Memfs2OpfsFS which is backed by an OPFS fs.2db5d2d: Upgrade emsdk to 6.0.5v0.5.12Compare Source
Patch Changes
0641b37: Fix custom filesystems not receiving times set withFS.utime. Emscripten'sFS.utimecallssetattrwithatimeandmtime, but theBaseFilesystembridge only handled the oldertimestampfield, soutimeswas never called on OPFS AHP or any otherBaseFilesystem. Files restored from a tarball kept the time they were written instead of the time stored in the tarball.e752dbe: Run initdb withTZ=UTC, like the backend, so a new database getstimezone = 'UTC'inpostgresql.conf. Before, initdb wrote the host's zone as a fixed offset without daylight saving (e.g.Etc/GMT+5for America/New_York), sotimestamptzinput without an offset was stored at a different instant on each non-UTC machine.c31130c: Start under the Node.js permission model (node --permission). Emscripten's NODEFS read the fs open flags withprocess.binding('constants'), which Node always denies in that mode, sonew PGlite()threwERR_ACCESS_DENIEDeven formemory://. The bundled build now reads them fromrequire('fs').constants, which holds the same values.0641b37: Fix files restored from a tarball getting a January 1970 modification time.loadTarpassed the tar header's time to Emscripten'sFS.utimein seconds, butFS.utimetakes milliseconds. This affected every new database (initdb's data dir is restored from a tarball) and everyloadDataDir. With the Node filesystem the files on disk got those dates too.v0.5.11Compare Source
Patch Changes
5573bb0: bug fix: check ready before close2372f39: Update submodule4321a41: Fix premature ReadyForQuery responses after extended-query errors, preventing PostgreSQL clients from desynchronizing before Sync.react-hook-form/resolvers (@hookform/resolvers)
v6.0.2Compare Source
Bug Fixes
v6.0.1Compare Source
Bug Fixes
Simple-With-Us/congress-trading-shared (@jaywedgeworth22/congress-trading-shared)
v2.9.0Compare Source
v2.8.1Compare Source
v2.8.0Compare Source
getsentry/sentry-javascript (@sentry/node)
v11.10.0Compare Source
Important Changes
feat: Add a managed tunnel that the SDK derives from the DSN (#25199, #25200, #25783)
Set
tunnel: truein your browserSentry.initcall to send events through your own server. This helps when ad blockers block requests to Sentry. The browser derives the tunnel path from the DSN, so older and newer builds of your client and server always agree on the path.To serve the tunnel, add
serveTunnelIntegration()to your server SDK. Astro, Nuxt, Nitro, React Router, Remix 3, SolidStart, SvelteKit and TanStack Start then answer tunnel requests automatically:If the browser uses a different DSN than the server, set
serveTunnelIntegration({ allowedDsns: [browserDsn] }). For other setups, the server SDKs exporthandleTunnelRequestIfMatched,handleTunnelRequest,isTunnelRequestandgetTunnelPath:The
requestoption ofhandleTunnelRequestis deprecated and will be removed in v12.feat: Make span origins spec compliant (#25602)
Some span origins changed their names to follow the trace origin spec:
auto.amqplib.*is nowauto.queue.amqplib.*, andauto.kafkajs.*is nowauto.queue.kafkajs.*.auto.vercelai.channelis nowauto.ai.vercelai.auto.firebase.firestoreis nowauto.db.firebase.firestore, andauto.firebase.functionsis nowauto.function.firebase.auto.aws.aws_sdkis nowauto.{rpc,db,queue,ai}.aws_sdk, with the category from the span op.auto.aws_lambdais nowauto.function.aws_serverless.auto.mcp.notificationis nowauto.function.mcp_server.notification.auto.db.cloudflare.durable_object.sqlis nowauto.db.cloudflare.durable_object_sql.auto.http.browser.{lcp,cls,inp}is nowauto.ui.browser.{lcp,cls,inp}.If you have
ignoreSpansrules, queries or alerts on the old origins, change them to use the new origins.feat(bun): Add incoming request options and request sessions to
bunServerIntegration(#25580)bunServerIntegrationnow 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(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.feat(cloudflare): Add incoming request span options to
httpServerIntegration(#25582)Cloudflare's
httpServerIntegrationnow acceptsignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreatedandonSpanEnd, with the same meaning as in the Node, Deno and Bun integrations. The callbacks receive the webRequest.ignoreStaticAssetsdefaults totrue, so workers no longer create spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, sethttpServerIntegration({ ignoreStaticAssets: false }). Request spans also follow the client's tracing configuration by default, so the SDK does not start them when tracing is disabled. IfignoreRequestBodythrows, the request no longer fails, and the SDK skips the body.feat(cloudflare): Let users configure the channel integrations (#25584)
When the
@sentry/cloudflare/viteplugin bundles an instrumented package (for examplepgoropenai), the SDK adds the matching integration with its default options.@sentry/cloudflarenow exports these integrations, so you can set their options, for example ininstrument.server.ts:These integrations need the vite plugin. Without it, they record nothing, and with
debug: truethe SDK logs a warning.feat(node): Add
onSpanEndtohttpIntegration(#25581)httpIntegrationandhttpServerSpansIntegrationnow 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(node, bun, deno, cloudflare): Align portable exports across server SDKs (#25583)
Node, Bun, Deno and Cloudflare now export the same helpers from
@sentry/coreand@sentry/server-utilswhere they work on that runtime:moduleMetadataIntegration,instrumentPostgresJsSql,instrumentCreateReactAgent,awsIntegrationand theFlueOptionstype.awsIntegrationwas already in their default integrations.parameterizeandinstrumentStateGraphCompile.LogandLogSeverityLeveltypes.fastifyIntegration, which was already in its default integrations.feat(nuxt): Start the server SDK on the Nuxt Vite server (experimental) (#25524)
Sentry now supports Node.js production builds using Nuxt 4.6's experimental Vite server (
server: { builder: 'vite' }). Yoursentry.server.configloads automatically, enabling request tracing and automatic database spans for supported libraries.Development mode, Cloudflare, automatic capture of server rendering errors, and connecting server and browser traces via HTML meta tags are not yet supported. This experimental support may change in minor releases.
ref(deno, bun): Use a shared request handler wrapper for
Deno.serveandBun.serve(#25586, #25587)Deno.serveandBun.servenow use the same request handler wrapper, which Cloudflare will also use. On both runtimes, errors inOPTIONSandHEADrequests now carry the request data, and the SDK keeps everySet-Cookieheader of a response instead of only the last one.For Deno users:
Bun.servespans now follow the Sentry conventions forhttp.serverspans, as on Node, Deno and Cloudflare:url.templateis nowhttp.route. Routes without parameters also gethttp.routeand theroutesource.url.domainis nowserver.address./gets theroutesource and the nameGET /.user_agent.originalandhttp.request.body.size.Other Changes
execute_toolspans for Anthropic'sbeta.sessions.events.toolRunner()(#25554)varin the Vite transform (#25663)defaultkeyword in the Vite transform (#25741)undicifetch andnode:http(#25441)Internal Changes
ServerRequestOptionstype across runtimes (#25579)GEN_AI_EXTRACTop from@sentry/conventions(#25734)Work in this release was contributed by @4ktLuffy, @faizansaiyed123, @itisrmk, @kunal649, @kyrylolvov, @larcane97, @lfantone, @pcbeingused333, @psh4607, and @seongwon030. Thank you for your contributions!
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
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.