Skip to content

merge queue: checking main (a620bcb) and #12319 together - #12332

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

merge queue: checking main (a620bcb) and #12319 together#12332
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/8e9734d7f1

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 (a620bcb) and #12319 are queued together for merge.

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

kozlek and others added 2 commits August 6, 2026 09:51
The engine renamed its documented-data-type flag from `x-has-data-type`
to `x-mergify-has-data-type`, matching the namespacing already used for
`x-mergify-enum`. An unprefixed `x-` key is a claim on a name nobody
owns, which is how `x-enum-descriptions` ended up meaning a positional
array of strings to openapi-generator and a map to us.

Read the new spelling only. The engine publishes both today, so this is
safe now — and reading only one is what makes dropping the other
possible: while a consumer accepts either, nothing can tell which it
actually depends on, so the removal can never be shown to be safe. This
is the step that unblocks it.

Only `isDataType` reads the flag — the anchor collector, both config
tables and the build gate all go through it — so this is one predicate,
not a sweep. The comments and the anchor-check message that named the
old key are updated with it; a marker's name appearing in prose that no
longer matches what the code looks for is how the next reader gets sent
after the wrong thing.

Part of MRGFY-8330

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