build(deps): Bump catalog @sentry/node to 10.64.0#803
Open
sergical wants to merge 1 commit into
Open
Conversation
Bumps the pnpm catalog pin for @sentry/node from 10.59.0 to 10.64.0 (current npm latest), updating all workspace consumers. Lockfile regenerated and prettier-formatted; diff is limited to the SDK and its transitive OpenTelemetry deps. Verified: repo-wide typecheck passes, @sentry/junior builds, and the lockfile validates under --frozen-lockfile. Unit/integration tests were not run here (they require the local Postgres test harness on :54322). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
|
does this fix something |
Member
Author
|
potentially - context in slack |
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
2 participants
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.
What
Bumps the pnpm
catalog:pin for@sentry/node10.59.0 → 10.64.0 (current npmlatest) inpnpm-workspace.yaml, updating every workspace consumer (@sentry/junior-sentry, core instrumentation, etc.).The lockfile was regenerated (
pnpm install --lockfile-only) and prettier-formatted to match the repo's committed style, so the diff is limited to the SDK bump and its transitive OpenTelemetry deps (~200 lines) — no cosmetic reformatting noise.Why
@sentry/nodepin was last set to10.59.0on 2026-06-23 in feat(instrumentation): Enable span streaming #629 ("Enable span streaming").10.64.0(2026-07-07, past the repo'sminimumReleaseAge: 1440gate).getsentry/marky) inherit whatever@sentry/nodejunior ships.Verification
pnpm -r typecheckpnpm --filter @sentry/junior buildpnpm install --frozen-lockfile:54322), which wasn't available in this environmentNotes / open question
10.59.0pin intentional (e.g., tied to the span-streaming work in feat(instrumentation): Enable span streaming #629)? If it's deliberately held, feel free to close. Otherwise this keeps the SDK current.🤖 Generated with Claude Code