Skip to content

merge queue: checking main (93c5b32) and #12334 together - #12336

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

merge queue: checking main (93c5b32) and #12334 together#12336
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/e2f2e2117d

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 (93c5b32) and #12334 are queued together for merge.

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

kozlek and others added 2 commits August 6, 2026 16:14
The engine flags a schema node as a documented data type, and on the
configuration side `ConfigOptions` turns that flag into a link to the
matching section of the data-types page. The API reference publishes the
same flag and did nothing with it: `BatchStatus.code` rendered its twelve
values with no explanation and no pointer to the section that explains
them — the state documenting it was meant to fix, on the page a reader
most likely arrives from.

That left the convention enforcing something nobody consumed. The build
fails when a marked title has no matching heading, so the anchor was
being maintained for a link the API side never rendered.

Render "see <data type>" beside the values. The values stay: an API
consumer needs to know what a field accepts, and the marker only says
their meaning is written up elsewhere.

The type label is deliberately left alone. Substituting a title for the
accepted values there is exactly the regression that hoisting shared
enums into components caused for fifteen query parameters, and a marked
type used as a parameter would reintroduce it.

The flag is read from the referring node as well as the `$ref` target,
because pydantic publishes it inline for an inlined type and as a `$ref`
sibling for a hoisted one.

Part of MRGFY-8330

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