Repository navigation
chore(cli): Upgrade @sentry/api to 0.400.0 - #1645
Merged
Merged
Conversation
0.400.0 is the first release with getsentry/sentry#128639, which withholds info_ids and warning_ids from the public replay `field` enum. It differs from 0.399.0 only in that enum, on the replay index and details endpoints. Assert that replay explore now offers replay_type and ota_updates.* and never requests info_ids or warning_ids. 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 23, 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.
Upgrades the CLI's
@sentry/apidependency from^0.399.0(#1643) to^0.400.0, the first release with getsentry/sentry#128639. That change withholdsinfo_idsandwarning_idsfrom the public replayfieldenum. The 0.400.0 types differ from 0.399.0 only in that enum, on the replay index and details endpoints.The lockfile change only covers
@sentry/api.pnpm-workspace.yamlmoves theminimumReleaseAgeExcludeentry to 0.400.0, because it was published today.Since #1617, replay explore builds its fields from the schema. New assertions in
test/lib/replay-search.test.tscheck that:replay_typeandota_updates.channelare supported.info_idsandwarning_idsare neither supported fields nor requestable roots.Verification: typecheck and lint pass, and a frozen-lockfile install passes. The replay, explore, and issue-app-links tests pass (149 tests). I didn't rerun the full suite, because the schema change is limited to that enum.
via BYK.
--
View Junior Session [Sentry]