Skip to content

chore(release): raise the tarball boot-smoke limit and align the lite pipeline tests - #19088

Merged
diegosouzapw merged 3 commits into
release/v3.8.53from
fix/release-v3.8.53-basereds-1105
Nov 5, 2026
Merged

diegosouzapw merged 3 commits into
release/v3.8.53from
fix/release-v3.8.53-basereds-1105

docs(changelog): number the pack-boot fragment after the PR

a18d535
Select commit
Loading
Failed to load commit list.
Mergify / Mergify Merge Queue completed Nov 5, 2026 in 1h 9m 10s

Dequeued — checks failed

❌ Left the queue · checks failed

1 h 9 min in the queue, less than a minute of it CI.

So far

  • ✅ Entered the queue Thu 5 Nov, 03:52 · rule release · triggered by merge protections
  • ❌ Checks failed · draft #19101
  • 🚫 Left the queue 05:01 · a18d535

The failure is in this pull request. It failed tested alone on top of release/v3.8.53.

Reason

The merge conditions cannot be satisfied due to failing checks

To get back in the queue

  • Push a fix: the pull request is queued again once its queue conditions match.
  • If the failure is a flake, tick the box below to queue it again as it is.

Merge conditions not met when it left the queue

  • #check-success>=1
  • check-success=Gate / CI
  • check-success=Gate / Quality
  • check-success=Merge integrity (changelog + generated skills)

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

  • Requeue this pull request
3 merge conditions met
  • #check-pending=0
  • github-review-approved · required by GitHub repository ruleset rule Require PR on default branch
  • any of:
    • #check-failure=0
    • all of:
      • #check-failure=1
      • check-failure=Build (advisory)

Times in UTC · dashboard · how the merge queue works