merge queue: checking #389 on main (75d603a)

[mergify]

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch used-civet-cje4j7 of the default queue, to test #389 before it merges into main. Pushing to this branch or closing this pull request removes #389 from the queue.

What this draft tests

Mergify checks that #389 still passes CI on top of main. CI runs on this draft's code, built in this order:

1. main at 75d603a
2. #389, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the default queue in the dashboard

What happens next

• Mergify merges #389 into main and closes this draft.

Metadata for CI tooling, read by mergify ci

---
all_scopes: false
checking_base_sha: 75d603ab555a2e6e44ae61eec66da32c7d261ca1
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 389
    scopes: []
scopes: []
...

Required conditions of queue rule default for merge

• #review-threads-unresolved=0
  • chore(cli): CTC-5458 — release publisher fix in 0.16.16 #389
• base=main
• check-success=check
• label!=hold
  • chore(cli): CTC-5458 — release publisher fix in 0.16.16 #389
• all of [🛡 Merge Protections rule no unresolved review threads before merge]:
  • #review-threads-unresolved=0
    • chore(cli): CTC-5458 — release publisher fix in 0.16.16 #389

Required conditions to stay in the queue

• #review-threads-unresolved=0
  • chore(cli): CTC-5458 — release publisher fix in 0.16.16 #389
• -draft
  • chore(cli): CTC-5458 — release publisher fix in 0.16.16 #389
• base=main
  • chore(cli): CTC-5458 — release publisher fix in 0.16.16 #389
• check-success=check
  • chore(cli): CTC-5458 — release publisher fix in 0.16.16 #389
• label!=hold
  • chore(cli): CTC-5458 — release publisher fix in 0.16.16 #389
• all of [🛡 Merge Protections rule no unresolved review threads before merge]:
  • #review-threads-unresolved=0
    • chore(cli): CTC-5458 — release publisher fix in 0.16.16 #389