Skip to content

merge queue: checking main (a32dfe1) and #1723 together#1727

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

merge queue: checking main (a32dfe1) and #1723 together#1727
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/95125b6fe1

Conversation

@mergify

@mergify mergify Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

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

Branch main (a32dfe1) and #1723 are queued together for merge.

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

sileht and others added 2 commits July 17, 2026 17:24
…y renames

`queue_metadata::parse_yaml_block` modeled the MQ draft-PR-body payload
with a rigid serde struct whose `draft_pr_number` was required. The
engine (MRGFY-8075) renamed that key to `batch_pr_number` and dual-emits
both for one release window before dropping the old spelling. A missing
required field fails the *whole document*, and the caller's `.ok()`
swallows that into `None`, so once the alias is gone every batch body
with a non-empty `previous_failed_batches` would silently cost `git-refs`
its `checking_base_sha` and diff against the wrong base, with no error
surfaced anywhere.

That struct has been dead code since #1600: its only reader, `git_refs`,
uses just `checking_base_sha`; every other field is parsed and discarded.
So rather than a `#[serde(alias)]` band-aid on one key, parse the payload
into a generic `serde_json::Value` — exactly how the git-note twin
(`git::read_note`) already reads the identical payload — and pull
`checking_base_sha` out with the existing shared helper. The CLI is now
immune to any engine key rename in this block, with no schema left to
drift and no call-site churn.

While here: warn instead of silently falling through to the PR base when
MQ metadata is present but carries no `checking_base_sha`, so a future
rename of that key can't degrade the base silently either; and share the
YAML-mapping parse between the note and PR-body readers so they can't
diverge in what they accept.

Fixes MRGFY-8104

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I6732b7057db0c98a7bb275d95fbd6470e39bad8b
@mergify
mergify Bot deployed to Mergify Merge Protections July 20, 2026 07:45 Active
@mergify
mergify Bot temporarily deployed to func-tests-live July 20, 2026 07:45 Inactive
@mergify mergify Bot closed this Jul 20, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/95125b6fe1 branch July 20, 2026 07:52
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