-
-
Notifications
You must be signed in to change notification settings - Fork 207
fix(deps): update dependency @sentry/node to v10 #2872
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
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-sentry-javascript-monorepo
base: master
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 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
Contributor
🚀 Snapshot Release (
|
| Package | Version | Info |
|---|---|---|
@graphql-inspector/action |
5.0.9-alpha-20251105194939-9be43484ab630fd5257c476d97a83d88d03fe3da |
npm ↗︎ unpkg ↗︎ |
@graphql-inspector/cli |
5.0.9-alpha-20251105194939-9be43484ab630fd5257c476d97a83d88d03fe3da |
npm ↗︎ unpkg ↗︎ |
@graphql-inspector/audit-command |
5.0.9-alpha-20251105194939-9be43484ab630fd5257c476d97a83d88d03fe3da |
npm ↗︎ unpkg ↗︎ |
@graphql-inspector/coverage-command |
6.1.3-alpha-20251105194939-9be43484ab630fd5257c476d97a83d88d03fe3da |
npm ↗︎ unpkg ↗︎ |
@graphql-inspector/diff-command |
5.0.9-alpha-20251105194939-9be43484ab630fd5257c476d97a83d88d03fe3da |
npm ↗︎ unpkg ↗︎ |
@graphql-inspector/introspect-command |
5.0.9-alpha-20251105194939-9be43484ab630fd5257c476d97a83d88d03fe3da |
npm ↗︎ unpkg ↗︎ |
@graphql-inspector/similar-command |
5.0.9-alpha-20251105194939-9be43484ab630fd5257c476d97a83d88d03fe3da |
npm ↗︎ unpkg ↗︎ |
@graphql-inspector/validate-command |
5.0.9-alpha-20251105194939-9be43484ab630fd5257c476d97a83d88d03fe3da |
npm ↗︎ unpkg ↗︎ |
@graphql-inspector/core |
6.3.0-alpha-20251105194939-9be43484ab630fd5257c476d97a83d88d03fe3da |
npm ↗︎ unpkg ↗︎ |
Contributor
💻 Website PreviewThe latest changes are available as preview in: https://pr-2872.graphql-inspector.pages.dev |
aea1855 to
c1b2065
Compare
c1b2065 to
b72f686
Compare
b72f686 to
b3288de
Compare
b3288de to
b209014
Compare
b209014 to
8536389
Compare
8536389 to
c6ae297
Compare
c6ae297 to
2d6dc39
Compare
2d6dc39 to
8684c2a
Compare
8684c2a to
432b786
Compare
432b786 to
b27dab2
Compare
b27dab2 to
905ae71
Compare
905ae71 to
ff27f30
Compare
ff27f30 to
3396708
Compare
08b20fe to
ff67cdb
Compare
7993e80 to
8092613
Compare
8092613 to
178c122
Compare
178c122 to
89fb8a0
Compare
89fb8a0 to
47a780f
Compare
47a780f to
1bf5f6f
Compare
1bf5f6f to
7f47a47
Compare
7f47a47 to
0d92b5d
Compare
0d92b5d to
43751ce
Compare
43751ce to
263388f
Compare
bdbcacb to
26315af
Compare
26315af to
9f486c9
Compare
9f486c9 to
49b0cf3
Compare
49b0cf3 to
9be4348
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:
8.49.0->10.23.0Release Notes
getsentry/sentry-javascript (@sentry/node)
v10.23.0Compare Source
user-agentheader with envelope requests in server SDKs (#17929)maxValueLength: 250(#18043)optionsparameter optional onattachErrorHandler(#18072)internal_errorinstead ofunknown_error(#17909)Internal Changes
Work in this release was contributed by @hanseo0507. Thank you for your contribution!
Bundle size 📦
v10.22.0Compare Source
Important Changes
feat(node): Instrument cloud functions for firebase v2 (#17952)
We added instrumentation for Cloud Functions for Firebase v2, enabling automatic performance tracking and error monitoring. This will be added automatically if you have enabled tracing.
feat(core): Instrument LangChain AI (#17955)
Instrumentation was added for LangChain AI operations. You can configure what is recorded like this:
Other Changes
err(#17999)/when getting pathname (#17985)spanEndfor potentially cancelled lazy-route transactions (#17962)Internal Changes
getMetaTagTransformertests for Vitest compatibility (#18013)createHashRouter(#17789)Bundle size 📦
v10.21.0Compare Source
Important Changes
feat(browserProfiling): Add
tracelifecycle mode for UI profiling (#17619)Adds a new
tracelifecycle mode for UI profiling, allowing profiles to be captured for the duration of a trace. Amanualmode will be added in a future release.feat(nuxt): Instrument Database (#17899)
Adds instrumentation for Nuxt database operations, enabling better performance tracking of database queries.
feat(nuxt): Instrument server cache API (#17886)
Adds instrumentation for Nuxt's server cache API, providing visibility into cache operations.
feat(nuxt): Instrument storage API (#17858)
Adds instrumentation for Nuxt's storage API, enabling tracking of storage operations.
Other Changes
onRequestSpanEndhook to browser tracing integration (#17884)clean-css(#17979)Internal Changes
Work in this release was contributed by @0xbad0c0d3. Thank you for your contribution!
Bundle size 📦
v10.20.0Compare Source
Important Changes
feat(flags): Add Growthbook integration (#17440)
Adds a new Growthbook integration for feature flag support.
feat(solid): Add support for TanStack Router Solid (#17735)
Adds support for TanStack Router in the Solid SDK, enabling better routing instrumentation for Solid applications.
feat(nextjs): Support native debugIds in turbopack (#17853)
Adds support for native Debug IDs in Turbopack, improving source map resolution and error tracking for Next.js applications using Turbopack. Native Debug ID generation will be enabled automatically for compatible versions.
Other Changes
pinologger name (#17930)POPguard for long-runningpageloadspans (#17867)Internal Changes
- chore(nextjs): Add Next.js 16 peer dependency ([#17925](https://redirect.github.com/getsentry/sentry-javascript/pull/17925)) - chore(ci): Update Next.js canary testing ([#17939](https://redirect.github.com/getsentry/sentry-javascript/pull/17939)) - chore: Bump size limit ([#17941](https://redirect.github.com/getsentry/sentry-javascript/pull/17941)) - test(nextjs): Add next@16 e2e test ([#17922](https://redirect.github.com/getsentry/sentry-javascript/pull/17922)) - test(nextjs): Update next 15 tests ([#17919](https://redirect.github.com/getsentry/sentry-javascript/pull/17919)) - chore: Add external contributor to CHANGELOG.md ([#17915](https://redirect.github.com/getsentry/sentry-javascript/pull/17915)) - chore: Add external contributor to CHANGELOG.md ([#17928](https://redirect.github.com/getsentry/sentry-javascript/pull/17928)) - chore: Add external contributor to CHANGELOG.md ([#17940](https://redirect.github.com/getsentry/sentry-javascript/pull/17940))Work in this release was contributed by @seoyeon9888, @madhuchavva and @thedanchez. Thank you for your contributions!
v10.19.0Compare Source
Internal Changes
v10.18.0Compare Source
Important Changes
feat(node):
pinointegration (#17584)This release adds a new
pinointegration for Node.js, enabling Sentry to capture logs from the Pino logging library.feat: Remove @sentry/pino-transport package (#17851)
The
@sentry/pino-transportpackage has been removed. Please use the newpinointegration in@sentry/nodeinstead.feat(node-core): Extend onnhandledrejection with ignore errors option (#17736)
Added support for selectively suppressing specific errors with configurable logging control in onnhandledrejection integration.
Other Changes
sentry.client.config.tsin nuxt app types (#17830)OriginalHandleRequestwith middleware (#17870)Internal Changes
Work in this release was contributed by @stefanvanderwolf. Thank you for your contribution!
v10.17.0Compare Source
Important Changes
feat(nuxt): Implement server middleware instrumentation (#17796)
This release introduces instrumentation for Nuxt middleware, ensuring that all middleware handlers are automatically wrapped with tracing and error reporting functionality.
fix(aws-serverless): Take
http_proxyinto account when choosinguseLayerExtensiondefault (#17817)The default setting for
useLayerExtensionnow considers thehttp_proxyenvironment variable.When
http_proxyis set,useLayerExtensionwill be off by default.If you use a
http_proxybut would still like to make use of the Sentry Lambda extension, exemptlocalhostin ano_proxyenvironment variable.Other Changes
beforeSendSpan(#17815)Internal Changes
v10.16.0Compare Source
replay_is_bufferingflag (#17752)instrumentAnthropicAiClientbreaking MessageStream api (#17754)Internal Changes
publish_releasecommand (#17797)import-in-the-middlewhen building the Lambda layer (#17780)[email protected]due to@vercel/nftincompatibility (#17777)" (#17784)[email protected]due to@vercel/nftincompatibility (#17777)v10.15.0Compare Source
Important Changes
feat(cloudflare): Add honoIntegration with error-filtering function (#17743)
This release adds a
honoIntegrationto@sentry/cloudflare, which exposes ashouldHandleErrorfunction that lets you define which errors inonErrorshould be captured.By default, Sentry captures exceptions with
error.status >= 500 || error.status <= 299.The integration is added by default, and it's possible to modify this behavior like this:
feat(node): Add instrumentation for hono handler (#17428)
This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities.
feat(aws): Enable Lambda extension by default when using the Lamba layer (#17684)
feat(browser): Add
setActiveSpanInBrowserto set an active span in the browser (#17714)This PR adds a feature to the browser SDKs only: Making an inactive span active. We do this to enable use cases where having a span only being active in the callback is not practical.
Other Changes
0andundefinedresource timing values (#17751)Internal Changes
@typescript-eslint/no-unnecessary-type-assertionrule (#17728)es2020everywhere (#17709)Work in this release was contributed by @Karibash. Thank you for your contribution!
v10.14.0Compare Source
Important Changes
feat(cloudflare,vercel-edge): Add support for Google Gen AI instrumentation (#17723)
The SDK now supports manually instrumenting Google's Gen AI operations in Cloudflare Workers and Vercel Edge Runtime environments, providing insights into your AI operations. You can use
const wrappedClient = Sentry.instrumentGoogleGenAIClient(genAiClient)to get an instrumented client.Other Changes
WeakRefwhen storing it on spans (#17712)Internal Changes
v10.13.0Compare Source
Important Changes
feat(browser): Add option to explicitly end pageload span via
reportPageLoaded()(#17697)With this release you can take manual control of ending the pageload span. Usually this span is ended automatically by the SDK, based on a period of inactivity after the initial page was loaded in the browser. If you want full control over the pageload duration, you can tell Sentry, when your page was fully loaded:
Note that if
Sentry.reportPageLoaded()is not called within 30 seconds of the initial pageload (or whatever value thefinalTimeoutoption is set to), the pageload span will be ended automatically.feat(core,node): Add instrumentation for
GoogleGenAI(#17625)The SDK now automatically instruments the
@google/genaipackage to provide insights into your AI operations.feat(nextjs): Promote
useRunAfterProductionCompileHookto non-experimental build option (#17721)The
useRunAfterProductionCompileHookoption is no longer experimental and is now a stable build option for Next.js projects.feat(nextjs): Use
afterProductionCompilehook for webpack builds (#17655)Next.js projects using webpack can opt-in to use the
useRunAfterProductionCompileHookhook for source map uploads.feat(nextjs): Flip default value for
useRunAfterProductionCompileHookfor Turbopack builds (#17722)The
useRunAfterProductionCompileHookoption is now enabled by default for Turbopack builds, enabling automated source map uploads.feat(node): Do not drop 300 and 304 status codes by default (#17686)
HTTP transactions with 300 and 304 status codes are now captured by default, providing better visibility into redirect and caching behavior.
Other Changes
onSuccesstohandleCallbackErrors(#17679)consoleLoggingIntegration(#17703)oscontext (#17720)thirdPartyErrorFilterIntegration(#17693)thiscontext for vercel AI instrumentation (#17681)Internal Changes
reportPageLoaded(#17724)getTestMatrix(#17673)SyncPromisewhere not needed (#17641)ignoreSpans(#17692)module_metadataassignment and cleanup functions (#17696)HandleDocumentRequestFunction(#17680)Work in this release was contributed by @Olexandr88. Thank you for your contribution!
v10.12.0Compare Source
Important Changes
ref: Add and Adjust error event
mechanismvaluesThis release includes a variety of changes aimed at setting the
mechanismfield on errors captured automatically by the Sentry SDKs. The intention is to clearly mark which instrumentation captured an error. In addition, some instrumentations previously did not yet annotate the error as handled or unhandled which this series of PRs corrects as well.Relevant PRs
Released in
10.12.0:mechanismon error events captured by astro middleware (#17613)mechanismof errors captured in Bun.serve (#17616)mechanismsand durable object origin (#17618)mechanismincaptureConsoleIntegration(#17633)mechanism(#17622)linkedErrorsmechanism logic (#17600)mechanismof errors caught byglobalHandlersIntegration(#17635)mechanisms (#17543)mechanismto cron instrumentations (#17544)mechanism.typeto worker thread errors fromchildProcessIntegration(#17578)mechanismofonUnhandledRejectionandonUnhandledExceptionintegrations (#17636)mechanism.typein error events (#17599)reactErrorHandlerand adjust mechanism inErrorBoundary(#17602)captureRemixServerException(#17629)replayIntegrationin debug mode (#17606)mechanismto error captured bywithSentryErrorBoundary(#17607)mechanismof error events (#17646)Released in
10.11.0:mechanism.typeto errors captured byhttpClientIntegration(#17254)mechanism.typeinbrowserApiErrorsIntergation(#17251)mechanism.typetotrpcMiddlewareerrors (#17287)mechanisms and span origins toopenAiIntegration(#17288)mechanismto captured errors (#17312)prismaIntegrationworks with Prisma 5 (#17595)We used to require to pass in the v5 version of
@prisma/instrumentationintoprismaIntegration({ prismaInstrumentation: new PrismaInstrumentation() }), if you wanted to get full instrumentation for Prisma v5. However, it turns out this does not work on v10 of the SDK anymore, because@prisma/instrumentation@5requires OTEL v1.With this release, we dropped the requirement to configure anything to get v5 support of Prisma. You do not need to configure anything in the integration anymore, and can remove the dependency on
@prisma/instrumentation@5if you had it in your application. You only need to configure thetracingpreview feature according to our docs.Other Changes
TracesSamplerSamplingContexttype (#17523)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 this update again.
This PR was generated by Mend Renovate. View the repository job log.