Skip to content

chore: update control openapi spec#1389

Open
knock-eng-bot wants to merge 1 commit intomainfrom
control-openapi-spec-updates
Open

chore: update control openapi spec#1389
knock-eng-bot wants to merge 1 commit intomainfrom
control-openapi-spec-updates

Conversation

@knock-eng-bot
Copy link
Copy Markdown
Contributor

Automated PR created from GitHub Actions workflow from knocklabs/control release (v0.1.1339).

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 10, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Apr 10, 2026 6:13pm

Request Review

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk MEDIUM: Automated OpenAPI spec update adds a new tenant query parameter to translation-related API endpoints.

Reasons

  • Only one file changed (data/specs/mapi/openapi.yml) with 29 additions and 0 deletions, which is a small diff
  • The change modifies an OpenAPI spec file under data/specs/, which triggers MEDIUM risk per classification rules even though it is automated
  • No component, layout, config, or package changes — no HIGH risk triggers
  • The PR is from the trusted bot knock-eng-bot via an automated GitHub Actions workflow (knocklabs/control release v0.1.1339)
  • Changes are additive only (new optional tenant parameter), reducing the chance of breaking existing behavior

Notes

  • Verify that the new tenant query parameter renders correctly on the API reference pages for the affected translation endpoints
  • Confirm the parameter descriptions are consistent across the three endpoints where it was added (list, get/put, and get translations)
  • No approval issued — MEDIUM risk PRs require human review even from trusted bots
Open in Web View Automation 

Sent by Cursor Automation: Docs PR classifier

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant