Skip to content

chore(deps): update JavaScript SDK to v10.77.1 - #6952

Draft
antonis wants to merge 3 commits into
mainfrom
antonis/bump-js-sdk-10.77.1
Draft

antonis wants to merge 3 commits into
mainfrom
antonis/bump-js-sdk-10.77.1

Conversation

@antonis

@antonis antonis commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

📢 Type of change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring

📜 Description

Bumps the bundled JavaScript SDK to the latest v10.77.1

The only breaking change in the release (limiting @opentelemetry/api to <1.10.0) affects the Node SDK packages, which are not used by the React Native SDK.

💡 Motivation and Context

Keep the JS layer in sync with the latest upstream sentry-javascript release v10. Note that the v11 is currently blocked #6773 and will be bumped on the next major.

💚 How did you test it?

CI, Manual

📝 Checklist

  • I added tests to verify changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • All tests passing.
  • Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.
  • No breaking changes.

🔮 Next steps

  • Update yarn.lock once 10.77.1 clears Yarn's package age quarantine.

🤖 Generated with Claude Code

antonis and others added 2 commits October 27, 2026 12:19
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).


  • chore(deps): update JavaScript SDK to v10.77.1 by antonis in #6952
  • feat(tracing): Track WebView trace-propagation feature adoption by antonis in #6938
  • build(deps): Bump body-parser to 2.4.0 to resolve DoS advisory by antonis in #6948
  • fix(android): Apply screenshot masking options to error and feedback screenshots by antonis in #6930
  • chore(deps): update Android SDK to v8.62.0 by github-actions in #6932
  • chore(deps): update Maestro to v2.12.0 by github-actions in #6945
  • chore(deps): bump getsentry/craft/.github/workflows/changelog-preview.yml from 2.35.0 to 3.0.0 by dependabot in #6944
  • chore(deps): bump the codeql-action group with 3 updates by dependabot in #6940
  • chore(deps): bump actions/upload-artifact from 7.0.1 to 7.0.2 by dependabot in #6941
  • chore(deps): bump fast-uri from 3.1.8 to 3.1.9 by dependabot in #6946
  • chore(deps): bump undici from 6.29.0 to 6.29.1 by dependabot in #6947
  • chore(deps): bump actions/setup-node from 7.0.0 to 7.1.0 by dependabot in #6943
  • chore(deps): bump ruby/setup-ruby from 1.327.0 to 1.334.0 by dependabot in #6942
  • chore(deps): bump ip-address from 10.7.2 to 10.7.4 by dependabot in #6939
  • chore(deps): update Wizard to v9.0.0 by github-actions in #6936
  • chore(deps): update CLI to v3.8.2 by github-actions in #6933
  • ci: Move CI off end-of-life Node versions to Node 22 by antonis in #6927

🤖 This preview updates automatically when you update the PR.

@antonis antonis added the ready-to-merge Triggers the full CI test suite label Oct 27, 2026
"@babel/preset-env": "^7.25.3",
"@babel/preset-typescript": "^7.18.6",
"@sentry/core": "10.76.2",
"@sentry/core": "10.77.1",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yarn.lock still resolves JS SDK 10.76.2 after package.json bump to 10.77.1

package.json pins were bumped to 10.77.1, but yarn.lock still resolves @sentry/* to 10.76.2 with no 10.77.1 entries—run yarn install and commit the lockfile so the bump actually takes effect (immutable CI installs will fail otherwise).

Evidence
  • dev-packages/e2e-tests/package.json (and packages/core / samples) now declare @sentry/core / related packages at 10.77.1.
  • yarn.lock still contains resolutions like @sentry/core@npm:10.76.2, @sentry/browser@npm:10.76.2, and @sentry/react@npm:10.76.2.
  • Workspace entry @sentry/react-native@workspace:packages/core in yarn.lock still depends on @sentry/browser|core|react|bundler-plugins at npm:10.76.2.
  • A search of yarn.lock finds zero occurrences of 10.77.1, and yarn.lock is not in the PR changed files.
Also found at 3 additional locations
  • packages/core/package.json:91-108
  • samples/react-native-macos/package.json:19-20
  • samples/react-native/package.json:48-85

Identified by Warden · code-review · YJ6-63C

Comment on lines +19 to +20
"@sentry/core": "10.77.1",
"@sentry/react": "10.77.1",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

package.json bumped to 10.77.1 but yarn.lock still pins 10.76.2

Run yarn up (or yarn install) and commit the updated yarn.lock; otherwise Yarn 4 immutable CI installs will fail and the repo still resolves 10.76.2.

Evidence
  • samples/react-native-macos/package.json (and other manifests) now request @sentry/core / @sentry/react 10.77.1.
  • yarn.lock has zero 10.77.1 entries and still resolves those packages at 10.76.2, including the @sentry/react-native workspace deps.
  • Root package.json pins Yarn 4.17.0; Yarn 4 enables immutable installs when CI=true, and dev-packages/e2e-tests/cli.mjs documents that default.
  • The repo’s own updater (scripts/update-package-json.sh) uses yarn up, which rewrites both manifests and yarn.lock.
Also found at 4 additional locations
  • dev-packages/e2e-tests/package.json:16-16
  • packages/core/package.json:91-96
  • samples/expo/package.json:26-50
  • samples/react-native/package.json:51-52

Identified by Warden · find-bugs · GX7-KSV

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-to-merge Triggers the full CI test suite

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant