PR delivery tracker

Follow a change from queue to its collected delivery evidence. Select any status icon for its full report.

• Coverage unknownWhole-PR coverage is unproved; release checks cover the services recorded by the publisher.
• Release checks passedChecks passed for the services recorded by the publisher; other affected services may still be unconfirmed.
• Read failed / stale / unknownA recent attempt can fail. Stale means no recent result. Unconfirmed targets are not counted as failed deployments.
• Publisher heldOpen for the reason and report creation time. The actual stop time is unknown; known pin merges remain visible.
• Observed queue positionRaw position first captured for the earliest known attempt. 0 is a captured value; ? means unknown. Initial entry rank is unproved.
• Rollout observedIndependent completion of the recorded required targets. Counts show confirmed targets, not failures.
• Current desired rolloutPersistent resources can be confirmed while required hooks, metadata, or cleanup remain unconfirmed. Open the badge for current gaps and explicitly labeled confirmation history.

Source times are displayed in your time zone using a 24-hour clock. Unknown T1 uses a marked provisional position. T4 is the earliest qualifying version or runtime observation collected so far for the change's scope. It does not prove full rollout, application health, readiness, or a user flow. T5 requires successful checks for the services recorded by the publisher. Backfill may supply an earlier T4 source time. These milestones do not establish the actual first arrival of the PR code in Dev; details distinguish earlier code presence from later publication evidence.

Dates use first enqueue time when known. Unknown enqueue times are filtered by their provisional queue-received time; their actual enqueue time remains unknown.