merge queue: checking #265 on main (a409789), stacked on #262, #266 and #263

[mergify]

✨ The pull request #265 has been manually updated. ✨

#265 is queued for merge on branch main (a409789).

Stacked behind 3 pull requests queued ahead of this batch, not part of it. These checks run on a tip that also carries their commits, so a failure here can come from them as much as from #265.

Queued ahead of this batch:

• #262
• #266
• #263

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

Required conditions of queue rule dependabot for merge:

• check-success = test-cross-platform (windows-2022, Windows)
• all of [🛡 Merge Protections rule Full CI must pass]:
  • check-success = test-cross-platform (windows-2022, Windows)
  • check-success = DCO
  • check-success = coverage
  • check-success = quality
  • check-success = test
  • check-success = test-cross-platform (macos-15, macOS)
  • check-success = test-cross-platform (ubuntu-22.04, Linux)
• check-success = DCO
• check-success = coverage
• check-success = quality
• check-success = test
• check-success = test-cross-platform (macos-15, macOS)
• check-success = test-cross-platform (ubuntu-22.04, Linux)
• github-review-approved [🛡 GitHub repository ruleset rule main]
  • chore(deps): bump cap-std from 4.0.2 to 4.0.3 #265
• github-review-approved [🛡 GitHub repository ruleset rule ossf_best_practices]
  • chore(deps): bump cap-std from 4.0.2 to 4.0.3 #265
• all of [🛡 Merge Protections rule Do not merge outdated PRs]:
  • #commits-behind <= 3
    • chore(deps): bump cap-std from 4.0.2 to 4.0.3 #265
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = @mergify/Mergify Merge Protections
  • check-skipped = @mergify/Mergify Merge Protections
  • check-success = @mergify/Mergify Merge Protections

Required conditions to stay in the queue:

• author = dependabot[bot]
  • chore(deps): bump cap-std from 4.0.2 to 4.0.3 #265
• base = main
• github-review-approved [🛡 GitHub repository ruleset rule main]
  • chore(deps): bump cap-std from 4.0.2 to 4.0.3 #265
• github-review-approved [🛡 GitHub repository ruleset rule ossf_best_practices]
  • chore(deps): bump cap-std from 4.0.2 to 4.0.3 #265
• label != do-not-merge
  • chore(deps): bump cap-std from 4.0.2 to 4.0.3 #265
• all of [🛡 Merge Protections rule Do not merge outdated PRs]:
  • #commits-behind <= 3
    • chore(deps): bump cap-std from 4.0.2 to 4.0.3 #265
• all of [🛡 Merge Protections rule Full CI must pass]:
  • check-success = DCO
  • check-success = coverage
  • check-success = quality
  • check-success = test
  • check-success = test-cross-platform (macos-15, macOS)
  • check-success = test-cross-platform (ubuntu-22.04, Linux)
  • check-success = test-cross-platform (windows-2022, Windows)
• any of [🛡 GitHub repository ruleset rule main]:
  • check-success = @mergify/Mergify Merge Protections
  • check-neutral = @mergify/Mergify Merge Protections
  • check-skipped = @mergify/Mergify Merge Protections

---
checking_base_sha: cf4b7592881d504fa9d8213d3c853eb5579fe075
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 265
    scopes: []
scopes: []
...

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 3524d462-9424-4759-a95a-9871242dd434

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!