Skip to content
This repository was archived by the owner on May 11, 2026. It is now read-only.

chore: upgrade @snapshot-labs/snapshot-sentry to v2#642

Open
wa0x6e wants to merge 1 commit into
masterfrom
chore/upgrade-snapshot-sentry-v2
Open

chore: upgrade @snapshot-labs/snapshot-sentry to v2#642
wa0x6e wants to merge 1 commit into
masterfrom
chore/upgrade-snapshot-sentry-v2

Conversation

@wa0x6e

@wa0x6e wa0x6e commented May 10, 2026

Copy link
Copy Markdown
Contributor

Bumps the snapshot-sentry dep to v2, which moves the Sentry SDK to v10 (snapshot-labs/snapshot-sentry#17).

Summary

  • Updates package.json to point at the in-flight v2 branch via git+ssh (the repo is private so bun's tarball API path returns 404).
  • Drops the Express app argument from initLogger() to match the v2 signature.
  • Regenerates bun.lock.

Why split

This is the upgrade-only step. The follow-up PR builds on this branch to start using the new ignoreErrors option (snapshot-labs/snapshot-sentry#18) to suppress expected client-side errors (unauthorized etc.) — replacing the per-repo helpers we currently carry.

Test plan

  • bun run lint clean
  • CI passes (note: pre-existing typecheck errors around db.queryAsync in test files predate this PR — surfaced by the bun migration, not by this change)

Pulls in @sentry/node v10 via the upgrade-sentry-v10 branch (see
snapshot-labs/snapshot-sentry#17). The v2 release drops the Express
app argument from initLogger().

The dep is referenced via git+ssh because the repo is private and
bun's tarball fetch path is unauthenticated.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant