Repository navigation
update rc openapi spec - #4549
Open
github-actions[bot] wants to merge 5 commits into
Open
github-actions[bot] wants to merge 5 commits into
github-actions[bot] wants to merge 5 commits into
Conversation
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.
update rc openapi spec
Note
Low Risk
Documentation-only OpenAPI updates; possible minor impact if clients depend on specific operationId strings.
Overview
Regenerates
content/operate/rc/api/api-reference/openapi.jsonwith no intended runtime API behavior changes.Data Integration proxy routes (wildcard and base
data-integration-workspacepaths):operationIdvalues are renumbered across HTTP methods (e.g. GET_2→proxyDataIntegrationWorkspace, PUT/POST/PATCH suffixes shuffled). Summaries, parameters, and paths are unchanged—this is tooling/codegen naming cleanup.Agent Memory store operations (
listMemoryStores, get store, create API key, delete API key, etc.): response status blocks are reordered in the document (same codes, descriptions, and schemas such asMemoryStoreListResponseandMemoryProblemDetails; only declaration order differs).Reviewers should treat this as OpenAPI doc sync: confirm generated client/docs consumers tolerate
operationIdrenames if anything keys off those names.Reviewed by Cursor Bugbot for commit a3fa790. Bugbot is set up for automated code reviews on this repo. Configure here.