Skip to content

merge queue: checking main (e6f5114) and #12263 together - #12333

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

merge queue: checking main (e6f5114) and #12263 together#12333
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/bb7fe7b15d

Conversation

@mergify

@mergify mergify Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

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

Branch main (e6f5114) and #12263 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #12263.
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: e6f51144b063df0d6ae7fb3deb1106c03e1fc9a3
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12263
    scopes: []
scopes: []
...

kozlek and others added 2 commits August 6, 2026 11:51
A batch's `status.code` appeared on the API reference as a bare list of
values with no explanation, and nowhere else in the docs. Readers seeing
a status in an API response, in the CLI, or on a dashboard chip had no
way to find out what it meant.

Add a Batch Status section to the data-types page, rendering a table
generated from the OpenAPI spec so the codes and their descriptions come
from the engine rather than being hand-maintained, and cross-reference it
from the monitoring and batches pages. The table goes through the shared
reader added earlier, so it already handles the shapes a synced schema
can arrive in — a `$ref` to a hoisted component in particular, which the
engine's enum deduplication produces.

Extend the anchor build gate to scan the API spec alongside the
configuration schema. This is the first data type marked in the API
spec, and schema syncs land as direct pushes to main, so the deploy
build is the only gate they pass through.

The bundled schemas are what the sync bot will deliver once the engine
side merges. They carry the per-value documentation as `x-mergify-enum`,
a positional array aligned with `enum` holding a description, an optional
display title and a deprecation flag, and the data-type marker under its
namespaced spelling. `x-enum-descriptions` is gone: that name is an
established openapi-generator convention for a positional array of
strings, and publishing a map under it would mislead the SDK generators
customers run against our spec.

Part of MRGFY-8330

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Change-Id: Ic5cd08016af10408a80c0d9f72b86dd61abc0a84
@mergify
mergify Bot deployed to Mergify Merge Protections August 6, 2026 14:03 Active
@mergify mergify Bot closed this Aug 6, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/bb7fe7b15d branch August 6, 2026 14:06
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