tr
TryGhost
GitHub
Ghost
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
Ghost
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
GitHub
Ghost
Workspace
Succeeded
30542
715c90e9 Fixed formatting of newsletter recovery tests ref https://linear.app/ghost/issue/BER-3929 Apply repository formatting to the provider payload assertions changed while rebasing the shutdown coverage.
by Jonatan Sv...
J
Succeeded
30542
01a54a40 Updated submission compatibility comments with explicit states ref https://linear.app/ghost/issue/BER-3929 Distinguish emails without recipient accounting from batches submitted before submission counts were recorded when describing retries and totals.
by Jonatan Sv...
J
Succeeded
30542
044ed6b8 Updated submission coverage for rebuilt legacy preparation ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Only already-started legacy sends retain unknown submission counts. Verify that preserved batches keep their old completion rule and rebuilt legacy emails receive full submission accounting.
by Jonatan Sv...
J
Succeeded
30542
02b6f790 Updated submission coverage for rebuilt legacy preparation ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Only already-started legacy sends retain unknown submission counts. Verify that preserved batches keep their old completion rule and rebuilt legacy emails receive full submission accounting.
by Jonatan Sv...
J
Succeeded
30542
1c5380ef Fixed submission failure reporting and incomplete count progress ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email A failed processed-at write could hide an already recorded recipient verification failure from the email status and Sentry. Check persisted batch counts after workers reject, retaining the original worker error when no integrity failure can be read. Only use historical progress fallback when both submission counts are missing. A partially missing pair receives no verified progress credit.
by Jonatan Sv...
J
Succeeded
30542
ed1f611d Improved batch submission with focused lifecycle steps ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Separate recipient loading, message submission, status persistence and reporting while preserving the existing retry and uncertain-outcome paths. Use the shared structured exclusion event and the raw non-retryable marker. Remove inferred classifications for persisted verification failures, document the reusable message contract, and consolidate integration fixtures.
by Jonatan Sv...
J
Succeeded
30542
793e0301 Updated submission verification to preserve explicit error kinds ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Use the accounting helpers now provided by recipient preparation and state whether a failed invariant is a count discrepancy at each detection site. Preserve that classification when replaying persisted failures so ownership diagnostics cannot trigger the recipient-count alert. Separate persisted failure handling and completion reporting from submission verification, with regression coverage for replaying an ownership failure.
by Jonatan Sv...
J
Succeeded
30542
99ab9afe Updated submission accounting integration fixtures for TypeScript ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Type the submission-specific test doubles and query results after the preparation suite conversion. Preserve distinct verification and uncertain submission error shapes while checking nullable status results explicitly.
by Jonatan Sv...
J
Succeeded
30542
e1a34900 Updated submission accounting integration fixtures for TypeScript ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Type the submission-specific test doubles and query results after the preparation suite conversion. Preserve distinct verification and uncertain submission error shapes while checking nullable status results explicitly.
by Jonatan Sv...
J
Succeeded
30542
b2fb6203 Updated submission accounting integration fixtures for TypeScript ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Type the submission-specific test doubles and query results after the preparation suite conversion. Preserve distinct verification and uncertain submission error shapes while checking nullable status results explicitly.
by Jonatan Sv...
J
Succeeded
30542
1c70ad5a Added source logging for newsletter submission count mismatches ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email ref https://linear.app/ghost/issue/BER-3898/alert-when-there-is-a-discrepancy-between-emailsemail-count-email Emit a dedicated P1 event for known unequal counts before status persistence can fail, while keeping invalid metadata and recovered reads outside it. Include batch IDs and successful provider message IDs for correlation, and document the structured fields SRE can use without parsing error strings.
by Jonatan Sv...
J
Failed
30542
1c70ad5a Added source logging for newsletter submission count mismatches ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email ref https://linear.app/ghost/issue/BER-3898/alert-when-there-is-a-discrepancy-between-emailsemail-count-email Emit a dedicated P1 event for known unequal counts before status persistence can fail, while keeping invalid metadata and recovered reads outside it. Include batch IDs and successful provider message IDs for correlation, and document the structured fields SRE can use without parsing error strings.
by Jonatan Sv...
J
Failed
30542
8d25b0f9 Fixed integrity reporting when shutdown leaves batches unstarted ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Inspect persisted batch outcomes during interrupted submission without rescanning recipients. Keep actionable error copy in the existing banner and rely on the verified preparation and batch identities for aggregate accounting.
by Jonatan Sv...
J
Succeeded
30542
51a085d5 Fixed integrity reporting when shutdown leaves batches unstarted ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Inspect persisted batch outcomes during interrupted submission without rescanning recipients. Keep actionable error copy in the existing banner and rely on the verified preparation and batch identities for aggregate accounting.
by Jonatan Sv...
J
Succeeded
30542
65c9f5c0 Fixed duplicate integrity reporting and unverified batch diagnostics ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Report terminal integrity failures once from the email job, identify batches with unknown submission counts, and keep integrity failures ahead of orphan diagnostics. Cover legacy submission counts and API serialization of all-excluded batches.
by Jonatan Sv...
J
Succeeded
30542
437b888e Fixed submission accounting retry and progress edge cases ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Count explicit validation exclusions, reject missing expected counts before submission, use the pre-send budget for rendering, and ignore stale verification diagnostics on batches that have left failed status. Keep failed progress readable without persisting inferred counts.
by Jonatan Sv...
J
Failed
30542
1e30d14b Added nonzero exclusion coverage across newsletter retries ref https://linear.app/ghost/issue/BER-3929/verify-recipient-counts-during-sending-before-marking-an-email Verify that rendering and provider retries preserve one explicit exclusion and report the invalid recipient once, while submitting the remaining recipient.
by Jonatan Sv...
J
Previous
Next