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
BYK
enabled auto-merge (squash)
October 23, 2026 22:34
7 tasks done
joshuawayzwright
pushed a commit
to joshuawayzwright/sentry-mcp
that referenced
this pull request
Nov 16, 2026
## Summary Malformed bearer credentials can be echoed by runtime header-validation errors. Normalize access tokens and reject invalid formatting before constructing authenticated API, Docs, init, and artifact-download requests. Failures use a fixed `AUTH_INVALID` message without the credential and preserve exit code 12. Share one helper for trimming surrounding whitespace and ASCII controls. Internal whitespace, controls, and non-ASCII characters remain invalid; split lines are never joined. Environment selection, token host claims, and cache `Vary` metadata use the same trimming rules. Cache metadata only trims a candidate: validation waits until OAuth refresh and credential selection determine the token actually used. Validate access tokens before SQLite writes, including refreshed credentials. Reject a malformed explicit `auth login --token` before changing the host or clearing existing authentication. Legacy JSON migration skips malformed auth, migrates other settings, and retains the original file with a fixed recovery warning, so help, login, and logout remain usable. Malformed-token failures remain visible as safe `MalformedAuthTokenError` events without retaining the credential or original cause. They do not trigger auto-login or mark a session crashed; ordinary authentication failures keep their existing reporting policy. ## Validation - Full validation at `e754fb328`: 467 unit files, 10,050 passed / 14 skipped (`TZ=UTC`); 34 bundled E2E passed across auth, library, and migration; lint, TypeScript, and bundle build passed. - After test-only cleanup: all 102 affected unit tests and 14 auth E2E passed, along with Biome and `git diff --check`. Production code is unchanged; the full suite and build were not repeated locally. - Property and regression coverage for edge padding, internal invalid characters, auth precedence, OAuth refresh, cache metadata, and persistence. ## Separate work General output and telemetry redaction remains in getsentry#1640. SDK invocation isolation (getsentry#1645) and rc tokens truncated when copied into `process.env` (getsentry#1646) are separate fixes; this PR does not address those earlier input/lifecycle boundaries. Bundler consumers pinned to `sentry ^0.44.0` need a `0.44.x` backport or a dependency update after release.
joshuawayzwright
pushed a commit
to joshuawayzwright/sentry-mcp
that referenced
this pull request
Nov 16, 2026
## Summary Malformed bearer credentials can be echoed by runtime header-validation errors. Normalize access tokens and reject invalid formatting before constructing authenticated API, Docs, init, and artifact-download requests. Failures use a fixed `AUTH_INVALID` message without the credential and preserve exit code 12. Share one helper for trimming surrounding whitespace and ASCII controls. Internal whitespace, controls, and non-ASCII characters remain invalid; split lines are never joined. Environment selection, token host claims, and cache `Vary` metadata use the same trimming rules. Cache metadata only trims a candidate: validation waits until OAuth refresh and credential selection determine the token actually used. Validate access tokens before SQLite writes, including refreshed credentials. Reject a malformed explicit `auth login --token` before changing the host or clearing existing authentication. Legacy JSON migration skips malformed auth, migrates other settings, and retains the original file with a fixed recovery warning, so help, login, and logout remain usable. Malformed-token failures remain visible as safe `MalformedAuthTokenError` events without retaining the credential or original cause. They do not trigger auto-login or mark a session crashed; ordinary authentication failures keep their existing reporting policy. ## Validation - Full validation at `e754fb328`: 467 unit files, 10,050 passed / 14 skipped (`TZ=UTC`); 34 bundled E2E passed across auth, library, and migration; lint, TypeScript, and bundle build passed. - After test-only cleanup: all 102 affected unit tests and 14 auth E2E passed, along with Biome and `git diff --check`. Production code is unchanged; the full suite and build were not repeated locally. - Property and regression coverage for edge padding, internal invalid characters, auth precedence, OAuth refresh, cache metadata, and persistence. ## Separate work General output and telemetry redaction remains in getsentry#1640. SDK invocation isolation (getsentry#1645) and rc tokens truncated when copied into `process.env` (getsentry#1646) are separate fixes; this PR does not address those earlier input/lifecycle boundaries. Bundler consumers pinned to `sentry ^0.44.0` need a `0.44.x` backport or a dependency update after release.
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]