Skip to content

chore(deps): Bump @sentry/api to 0.425.0 - #1723

Merged
BYK merged 1 commit into
mainfrom
chore/bump-sentry-api
Oct 29, 2026
Merged

BYK merged 1 commit into
mainfrom
chore/bump-sentry-api

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

Bumps @sentry/api from 0.423.0 to 0.425.0, the latest published version. It changes the catalog entry and the minimumReleaseAgeExclude entry in pnpm-workspace.yaml, plus the lockfile.

What changes upstream

  • Pagination continuations (sentry-api-schema#115, build: Bump deps #116):
    • paginateUpTo now returns a serializable continuation, and accepts resume, so a batch can pick up inside a partly consumed page.
    • consumePage and CollectionPageFetcher let a caller reuse a page it already fetched.
    • BudgetedPageFetcher's second parameter is now the request budget. On a replay it repeats the original budget.
  • New module: source-analysis, which brings a new optional typescript peer. The lockfile resolves it to the existing typescript@5.9.3.
  • Everything else is additive:
    • types.gen.d.ts is unchanged.
    • No exports were removed.

Impact here

  • Nothing in this repo calls the changed helpers yet. That covers paginateUpTo, paginateAll, consumePage and fetchPage. unwrapPaginatedResult is used in cli/src/lib/api/alerts.ts and dashboards.ts, and its signature is unchanged. No code changes were needed.
  • toolkit-core's own pagination (paginate and fetchAllPages in toolkit-core/src/pagination.ts) is a separate implementation and isn't affected.
    • It already resumes inside a page by writing the consumed rows into the cursor's is_prev field. That keeps cursors as plain Sentry cursor strings, which the API and older CLIs still accept.
    • Moving it onto @sentry/api's object-based continuation is a possible follow-up for docs(openspec): Propose a shared Sentry API layer for the CLI and MCP #1669. It would mean deciding how to serialize the continuation for the CLI's --cursor and the MCP's cursor inputs, so I left it out of this bump.

Verification

  • pnpm install --frozen-lockfile is clean.
  • tsc --noEmit passes for toolkit-core, mcp-core, mcp-server, mcp-cloudflare and cli. That includes the CLI's regenerated SDK, which produces no diff.
  • toolkit-core: 270 tests pass. mcp-core: 1,885 pass, 6 skipped.
  • CLI unit tests: 11,760 pass. 7 fail in this sandbox:
    • 6 are the file-permission tests that also fail on clean main here (completions, telemetry, upgrade, code-scanner, file-changes).
    • The 7th, completions.property, failed because the gitignored completion-targets.json was stale after feat(cli): add issue tag distributions #1636. It passes after generate:completions, and CI regenerates that file.

The lockfile needed one workaround. pnpm checks the existing lockfile entries against minimumReleaseAge before it resolves anything. 0.423.0 is under the cutoff, and its exclusion is dropped in this PR, so a plain pnpm install refused to run. I removed the old @sentry/api entries and resolved again. The lockfile diff only swaps 0.423.0 for 0.425.0, with the published integrity hash.

via BYK.

--

View Junior Session in Sentry

Picks up pagination continuations (sentry-api-schema#115, #116). The
only new peer dependency is an optional typescript peer for the new
source-analysis module.

Co-Authored-By: BYK <burak.kaya@sentry.io>
@vercel

vercel Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sentry-local Ready Ready Preview Oct 29, 2026 1:53pm UTC

Request Review

@BYK
BYK merged commit cd44e74 into main Oct 29, 2026
42 checks passed
@BYK
BYK deleted the chore/bump-sentry-api branch October 29, 2026 14:57

This branch was successfully deployed

1 active deployment
Preview — 7c92be4a Deployed Oct 29, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: low PR risk score: low

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant