merge queue: embarking unstable (521be2b), #7737 and #8065 together

[mergify]

✨ Pull request #7737 which was ahead in the queue has been dequeued (for the following reason: checks failed). The pull request #8065 has been re-embarked. ✨

Branch unstable (521be2b), #7737 and #8065 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #8065.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

• check-success=local-testnet-success
• check-success=test-suite-success

Required conditions to stay in the queue:

• #approved-reviews-by >= 1
  • Fix reprocess queue memory leak #8065
• check-success=license/cla
• check-success=target-branch-check
• label!=do-not-merge
  • Fix reprocess queue memory leak #8065

---
checking_base_sha: d97ecbfc7ddfacff471e19edddaa2d221fd6c1a8
previous_failed_batches: []
pull_requests:
  - number: 8065
...

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ michaelsproul
✅ jimmygchen
❌ mergify[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ michaelsproul
✅ jimmygchen
❌ mergify[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}