chore(deps): update JavaScript SDK to v10.44.0#5832
Merged
Conversation
a4f3f50 to
dc7d247
Compare
Contributor
Author
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog.
🤖 This preview updates automatically when you update the PR. |
antonis
previously approved these changes
Mar 18, 2026
Contributor
antonis
left a comment
There was a problem hiding this comment.
LGMT!
- No React Native-specific changes — The 10.44.0 changelog is entirely about server-side/web packages: Effect.ts SDK (new), Astro 6, Hono, NestJS/BullMQ, NestJS/schedule, Node fetch headers. None of these touch mobile or React
Native code paths. - No breaking changes — This is a minor bump. The changelog shows only additive features and bug fixes. The fixes are in browser bot detection, Cloudflare, Next.js, Nuxt, and profiling-node — none relevant to RN.
- @sentry/core changes are benign — The core change is adding a sentry.timestamp.sequence attribute for timestamp tie-breaking (#19421), and a Vercel AI SDK fix. Neither affects the React Native SDK's usage of core.
- @sentry/browser fix — Skipping browserTracingIntegration setup for bot user agents (#19708). This only affects web browsers, not React Native's JS environment.
- Diff is mechanical — The actual code diff is just version bumps in package.json files and corresponding yarn.lock changes. No source code modifications in the RN SDK itself.
No risks identified. Safe to merge.
The eslint-config-sdk depends on eslint-plugin-import but ESLint 9 cannot resolve it from the transitive dependency location in CI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
The @typescript-eslint overrides were scoped to eslint-config-sdk 10.43.0 which no longer matched after the bump, causing @typescript-eslint v5 to be resolved instead of v8 and breaking ESLint. Also reverts the unnecessary eslint-plugin-import direct dependency since the root cause was the stale resolutions. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

Bumps scripts/update-javascript.sh from 10.43.0 to 10.44.0.
Auto-generated by a dependency updater.
Changelog
10.44.0
Important Changes
feat(effect): Add
sentry/effectSDK (Alpha) (#19644)This release introduces
sentry/effect, a new SDK for Effect.ts applications. The SDK provides Sentry integration via composable Effect layers for both Node.js and browser environments.Compose the
effectLayerwith optional tracing, logging, and metrics layers to instrument your Effect application:Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.
feat(astro): Add Astro 6 support (#19745)
This release enables full support for Astro v6 by adjusting our Astro SDK's middleware to some Astro-internal
changes. We cannot yet guarantee full support for server-islands, due to a bug in Astro v6
but we'll follow up on this once the bug is fixed.
feat(hono): Add basic instrumentation for Node runtime (#19817)
Adds a new package
sentry/hono/node(alpha) with basic instrumentation for Hono applications running in Node.js.The Hono middleware for Cloudflare (
sentry/hono/cloudflare- alpha) comes with fixes, and it's now possible to access the Cloudflare Worker Bindings (env) from the options' callback.Start using the new Hono middlewares by installing
sentry/honoand importing the respective middleware for your runtime.More instructions can be found in the Hono readme.
Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.
feat(nestjs): Instrument
nestjs/bullmqProcessordecorator (#19759)Automatically capture exceptions and create transactions for BullMQ queue processors in NestJS applications.
When using the
Processordecorator fromnestjs/bullmq, the SDK now automatically wraps theprocess()methodto create
queue.processtransactions with proper isolation scopes, preventing breadcrumb and scope leakage betweenjobs and HTTP requests. Errors thrown in processors are captured with the
auto.queue.nestjs.bullmqmechanism type.Requires
nestjs/bullmqv10.0.0 or later.feat(nestjs): Instrument
nestjs/scheduledecorators (#19735)Automatically capture exceptions thrown in
Cron,Interval, andTimeoutdecorated methods.Previously, exceptions in
Cronmethods were only captured if you used theSentryCrondecorator. Now they arecaptured automatically. The exception mechanism type changed from
auto.cron.nestjs.asynctoauto.function.nestjs.cron. If you have Sentry queries or alerts that filter on the old mechanism type, update themaccordingly.
feat(node): Expose
headersToSpanAttributesoption onnativeNodeFetchIntegration()(#19770)Response headers like
http.response.header.content-lengthwere previously captured automatically on outgoingfetch spans but are now opt-in since
opentelemetry/instrumentation-undici0.22.0. You can now configure whichheaders to capture via the
headersToSpanAttributesoption.Other Changes
sentry.timestamp.sequenceattribute for timestamp tie-breaking (#19421)sendDefaultPiisetting in langchain and langgraph in non-node environments (#19813)nestjs/event-emitterinstrumentation (#19725)lastEventIdwhen error is thrown in component render (#19764)Internal Changes
skill-creatorand update managed agent skills (#19713)sentry/honoalpha release (#19828)"*"(#19756)sdkNamefor craft (#19736)vite-plugin-federation(#19778)