Repository navigation
chore(openapi): regenerate API spec (2026-10-21) - #1001
Merged
Merged
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.
Automated regeneration of the CIPP OpenAPI spec, generated by
build/tools/build-openapi.ps1from the PowerShell AST of the HTTP entrypoints.The spec is not documentation-only:
Get-CippMcpSpecloads it at runtime andGet-CippMcpToolListprojects every read operation in it into an MCP tool, so a stale committed spec ships a stale tool contract.Operations: 739 -> 739
Added operations (1)
Removed operations (1)
Changed operations (2)
/api/AddUser/api/EditUserFiles changed
Opened by the Update OpenAPI Spec workflow. The
chore/openapi-spec-update-*branch is deleted on the next run once this PR is merged or closed.