chore: update @sentry/api to ^0.141.0#924
Draft
MathurAditya724 wants to merge 4 commits intomainfrom
Draft
Conversation
Picks up v0.141.0 which adds auto-generated Zod schemas via a new '@sentry/api/zod' subpath export (getsentry/sentry-api-schema#70).
Contributor
Codecov Results 📊✅ 6686 passed | Total: 6686 | Pass Rate: 100% | Execution Time: 0ms 📊 Comparison with Base Branch
✨ No test changes detected All tests are passing successfully. ✅ Patch coverage is 100.00%. Project has 13589 uncovered lines. Coverage diff@@ Coverage Diff @@
## main #PR +/-##
==========================================
- Coverage 76.66% 76.61% -0.05%
==========================================
Files 303 303 —
Lines 57997 58109 +112
Branches 0 0 —
==========================================
+ Hits 44463 44520 +57
- Misses 13534 13589 +55
- Partials 0 0 —Generated by Codecov Action |
Replace hand-written Zod schemas with auto-generated ones from @sentry/api/zod where the generated schemas cover the same response shapes. Keep custom schemas for internal/undocumented endpoints. Replaced: - SentryIssueSchema: derived from zRetrieveAnIssueResponse - IssueEventSchema: derived from zGroupEventsResponseDict element - SentryTeamSchema: derived from zBaseTeam Kept custom (with reasons): - Dashboard schemas: generated uses snake_case for input types (display_type, widget_type) while API responses use camelCase; DashboardDetailsModel widget layout is untyped Record<string,unknown> - Replay schemas: generated missing info_ids/warning_ids fields, custom .catch() fallback behavior for archived replays - Seer/Autofix schemas: generated autofix field is untyped Record<string,unknown> | null - Repository/Provider schemas: generated repo schema has only 3 fields vs CLI's 9; no provider sub-schema available - Internal schemas (regions, auth, logs, traces, spans, OAuth, config, DSN, sourcemaps, billing/trials): not in OpenAPI spec
Contributor
|
BYK
reviewed
May 6, 2026
| | `id` | string | Internal event ID | | ||
| | `event.type` | string | Event type (error, default, transaction) | | ||
| | `groupID` | string \| null | Group (issue) ID | | ||
| | `groupID` | unknown | | |
Member
There was a problem hiding this comment.
We need to fix all these unknown changes in references
Member
Author
There was a problem hiding this comment.
fixed in 73bbd09 — zodTypeToString didn't handle ZodUnion (which @sentry/api/zod uses for nullable fields instead of ZodNullable). Added union resolution + ZodRecord support, and re-added .describe() calls on all fields that lost descriptions when switching from hand-written to SDK schemas.
zodTypeToString now handles ZodUnion (used by @sentry/api/zod for nullable fields) and ZodRecord. Re-added .describe() calls on fields that lost descriptions when switching from hand-written to SDK schemas.
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.
Bumps
@sentry/apifrom^0.133.0to^0.141.0, picking up v0.141.0 which adds auto-generated Zod v3 schemas via a new@sentry/api/zodsubpath export (getsentry/sentry-api-schema#70).This makes auto-generated Zod schemas available for the CLI to use instead of the hand-written ones in
src/types/. The schemas stay in sync with the OpenAPI spec automatically on every@sentry/apirelease.Usage
Testing
bun run generate:schema && bun run generate:sdk && npx tsc --noEmit— typecheck passes.bun test test/lib/api-schema.test.ts— 19 tests pass.