Skip to content

merge queue: embarking main (eeac019) and #474 together#482

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

merge queue: embarking main (eeac019) and #474 together#482
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/c3a6deeb2a

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented May 21, 2026

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

Branch main (eeac019) and #474 are embarked together for merge.

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

sileht and others added 2 commits May 20, 2026 11:11
The "Upload to GitHub release assets" step ran `curl --fail` under
`set +e`, then only treated exit code 22 as a failure
(`if [ $? = 22 ]`). When GitHub returned 422, curl actually exited with
56 ("Failure in receiving network data" - curl aborts the HTTP/2
transfer mid-stream when `--fail` trips), so the `= 22` check never
matched. With errexit disabled the loop finished and the step exited 0,
turning a rejected upload green.

Drop the exit-code guessing: run curl in an `if !` so any non-zero exit
(22, 56, network errors) triggers `exit 1`, and use `--fail-with-body`
so GitHub's error payload (the 422 detail) stays visible in the logs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: Ia4cd0d86e9292735e26dffd2afacad1b6511ccd3
@mergify mergify Bot deployed to Mergify Merge Protections May 21, 2026 08:25 Active
@mergify mergify Bot closed this May 21, 2026
@mergify mergify Bot deleted the mergify/merge-queue/c3a6deeb2a branch May 21, 2026 08:28
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