Skip to content

merge queue: checking main (1bed144) and #12299 together - #12322

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/4e0897cfba
Closed

merge queue: checking main (1bed144) and #12299 together#12322
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/4e0897cfba

Conversation

@mergify

@mergify mergify Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (1bed144) and #12299 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #12299.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 1bed144484c12a69db97879b00fe961491b56204
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12299
    scopes: []
scopes: []
...

kozlek and others added 2 commits August 5, 2026 15:59
…enum

Deduplicating repeated enums in the OpenAPI spec hoists them into shared
components, so a query parameter's schema becomes a `$ref` instead of an
inline `enum`. `getTypeLabel` returned the component name for any `$ref`,
which is right for an object — the schema tree below expands it — but
wrong for an enum: parameters are rendered from that label alone, with no
tree underneath and no `enum` among their constraints.

Fifteen public parameters were affected. `/api/activity-log`'s
`event_type` listed all 44 accepted values and would have shown
`EventType[]`; `source` on the quarantines endpoint would have shown
`QuarantineSource` instead of `"manual" | "auto"`. The components
themselves are not rendered anywhere on the site, so the values would
have been published nowhere at all.

Resolve the reference when it targets an enum and keep the name
otherwise.

Part of MRGFY-8330

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Change-Id: Ic546133c44ed82ddc0f57c2269b64f6725247e27
@mergify
mergify Bot deployed to Mergify Merge Protections August 5, 2026 16:29 Active
@mergify mergify Bot closed this Aug 6, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/4e0897cfba branch August 6, 2026 07:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant