Repository navigation
ref(cli): Build agent conversation details schema from @sentry/api - #2121
Merged
Merged
Conversation
Take conversationId, title, and the stats fields the CLI reads from the generated vRetrieveOrganizationAiConversationResponse schema, so changes to those fields arrive with an @sentry/api bump. Spans keep the CLI's own schema because the spec types them as plain records, and stats stays nullish for later pages and older self-hosted servers. Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
BYK
approved these changes
Nov 9, 2026
This branch was previously 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.
Follow-up to #2108.
getConversationSpansalready calls the generatedretrieveOrganizationAiConversationoperation, but it validated the response with a schema written by hand. That schema drifted from the spec: upstream has typedstatsas nullable since the endpoint shipped, while the CLI typed it asoptional.AgentConversationDetailsSchemaandConversationStatsSchemanow take their field schemas fromvRetrieveOrganizationAiConversationResponse, the same wayTraceMetaSchemaand the timeseries schemas do. A change to those fields now arrives with an@sentry/apibump.Some parts still differ from the generated schema on purpose:
spanskeeps the CLI's span schema, because the spec types spans asrecord<unknown>.statsstaysnullish. The spec says it is required, but older self-hosted servers leave it out.usageByModelone at a time in Sep–Oct, so requiring them would reject recent self-hosted versions.projectsandwebUrlare not validated, because the CLI doesn't read them.via @BYK.
--
View Session in Sentry