Repository navigation
Share strict Sentry origin checks across CLI and MCP - #1444
Merged
Merged
Conversation
Co-Authored-By: GPT-6 Sol <agent@openai.com>
Co-Authored-By: GPT-6 Sol <agent@openai.com>
Co-Authored-By: GPT-6 Sol <agent@openai.com>
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
1 participant
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.
Summary
@sentry/toolkit-core/sentry-originand import it directly in CLI and MCP.Continues the incremental shared-core work in getsentry/cli#1247.
Validation
pnpm run tsc,pnpm run lint,pnpm run docs:check,pnpm run pre-commit:generatedpassed; repeated build/typecheck/lint after incorporating currentmain.pnpm run testreached 10,538 passing CLI tests, then exposed two stale MCP error-message assertions; updated both, and reran MCP-core: 1,757 passed, 6 skipped.