Repository navigation
chore(deps): Bump @sentry/api to 0.425.0 - #1723
Merged
Merged
Conversation
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>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
BYK
approved these changes
Oct 29, 2026
This branch was successfully deployed
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
@sentry/apifrom 0.423.0 to 0.425.0, the latest published version. It changes the catalog entry and theminimumReleaseAgeExcludeentry inpnpm-workspace.yaml, plus the lockfile.What changes upstream
paginateUpTonow returns a serializablecontinuation, and acceptsresume, so a batch can pick up inside a partly consumed page.consumePageandCollectionPageFetcherlet 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.source-analysis, which brings a new optionaltypescriptpeer. The lockfile resolves it to the existingtypescript@5.9.3.types.gen.d.tsis unchanged.Impact here
paginateUpTo,paginateAll,consumePageandfetchPage.unwrapPaginatedResultis used incli/src/lib/api/alerts.tsanddashboards.ts, and its signature is unchanged. No code changes were needed.paginateandfetchAllPagesintoolkit-core/src/pagination.ts) is a separate implementation and isn't affected.is_prevfield. That keeps cursors as plain Sentry cursor strings, which the API and older CLIs still accept.@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--cursorand the MCP's cursor inputs, so I left it out of this bump.Verification
pnpm install --frozen-lockfileis clean.tsc --noEmitpasses fortoolkit-core,mcp-core,mcp-server,mcp-cloudflareandcli. That includes the CLI's regenerated SDK, which produces no diff.toolkit-core: 270 tests pass.mcp-core: 1,885 pass, 6 skipped.mainhere (completions, telemetry, upgrade, code-scanner, file-changes).completions.property, failed because the gitignoredcompletion-targets.jsonwas stale after feat(cli): add issue tag distributions #1636. It passes aftergenerate:completions, and CI regenerates that file.The lockfile needed one workaround. pnpm checks the existing lockfile entries against
minimumReleaseAgebefore it resolves anything. 0.423.0 is under the cutoff, and its exclusion is dropped in this PR, so a plainpnpm installrefused to run. I removed the old@sentry/apientries 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