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
30541
48a927d1 Fixed newsletter retry claims and frozen recipient totals ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Keep retry refreshes within the claim transaction and preserve the claimed email relation when republishing. Treat a concurrent claim as a successful publish side effect while retaining direct retry API validation. Verify the stored preparation total and cover these failures against MySQL.
by Jonatan Sv...
J
Succeeded
30541
b3aed92a Fixed newsletter retry claims and frozen recipient totals ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Keep retry refreshes within the claim transaction and preserve the claimed email relation when republishing. Treat a concurrent claim as a successful publish side effect while retaining direct retry API validation. Verify the stored preparation total and cover these failures against MySQL.
by Jonatan Sv...
J
Succeeded
30541
613e0d45 Fixed retry responses to return persisted email timestamps ref https://linear.app/ghost/issue/BER-3927 The atomic status lock skips refresh for background jobs. Refresh the successful retry claim before scheduling so the API returns the database timestamp precision, as it did before the lock change.
by Jonatan Sv...
J
Succeeded
30541
21f29e01 Updated recipient preparation compatibility wording ref https://linear.app/ghost/issue/BER-3927 Name the persisted email state and its completion guarantees instead of using legacy as shorthand for different compatibility paths.
by Jonatan Sv...
J
Succeeded
30541
38808962 Changed recipient preparation to use one rebuild protocol ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Unsent historical emails can discard pending preparation safely. Persist accounting opt-in and rebuild them using the same verified flow as new emails. Preserve the full batch set for legacy sends that already started. Remove watermark reconciliation and the callback-based preparation loop. Move pagination and warming coverage onto the MySQL preparation suite, including conversion, crash recovery, and already-started legacy sends.
by Jonatan Sv...
J
Succeeded
30541
38808962 Changed recipient preparation to use one rebuild protocol ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Unsent historical emails can discard pending preparation safely. Persist accounting opt-in and rebuild them using the same verified flow as new emails. Preserve the full batch set for legacy sends that already started. Remove watermark reconciliation and the callback-based preparation loop. Move pagination and warming coverage onto the MySQL preparation suite, including conversion, crash recovery, and already-started legacy sends.
by Jonatan Sv...
J
Succeeded
30541
65d7c2b0 Improved preparation diagnostics and responsibility boundaries ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Distinguish invalid candidate metadata from recipient-row mismatches, keep exclusion accounting within the accounted path, and let legacy preparation load its own batches. Share frozen verification and exclusion diagnostics. Clarify logged error metadata and recovery conflicts, pin raw non-retryable error propagation, and cover empty totals and exclusions in warming slices.
by Jonatan Sv...
J
Succeeded
30541
234e65a8 Improved recipient accounting verification boundaries ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Check ownership in both directions before evaluating recipient counts so the same corruption has one diagnosis during cleanup and verification. Make count event classification explicit and mark terminal errors as non-retryable. Separate accounted preparation from legacy resume, return exclusion totals, share recipient validation, and isolate persisted submission verification. Remove the unused batch read and retain attempt and batch identities in logs. Cover zero-preflight sends, terminal retries, orphaned recipient totals and shutdown during preparation and cleanup. Consolidate test fixtures and record lock-wait observations outside retry stubs. Keep event contracts in public docs and incident procedures in the internal workspace.
by Jonatan Sv...
J
Succeeded
30541
7227d37e Changed recipient preparation integration coverage to TypeScript ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Use TypeScript for the new integration suite, with typed test fixtures and transaction handles while retaining the legacy Bookshelf runtime boundary.
by Jonatan Sv...
J
Succeeded
30541
7227d37e Changed recipient preparation integration coverage to TypeScript ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Use TypeScript for the new integration suite, with typed test fixtures and transaction handles while retaining the legacy Bookshelf runtime boundary.
by Jonatan Sv...
J
Succeeded
30541
7227d37e Changed recipient preparation integration coverage to TypeScript ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Use TypeScript for the new integration suite, with typed test fixtures and transaction handles while retaining the legacy Bookshelf runtime boundary.
by Jonatan Sv...
J
Failed
30541
b8380222 Added a dedicated event for confirmed recipient count mismatches ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation ref https://linear.app/ghost/issue/BER-3898/alert-when-there-is-a-discrepancy-between-emailsemail-count-email Separate count discrepancies from metadata and identity failures so P1 alerts can select known unequal counts without paging on every verification error.
by Jonatan Sv...
J
Succeeded
30541
77145d61 Fixed cross-email recipient ownership verification and shutdown reporting ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Reject ownership corruption before cleanup and catch balanced swaps without losing checks for foreign rows. Report verification failures during shutdown and preserve original transaction test failures.
by Jonatan Sv...
J
Succeeded
30541
753a0ac2 Fixed warming exclusion fixture to cover both sending domains ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Exclude the first consumed candidate in the descending sweep so the recovery assertion exercises both custom and fallback batches.
by Jonatan Sv...
J
Failed
30541
4ec0886b Fixed preparation recovery diagnostics and coverage ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Distinguish safely rebuildable preparation errors, retain audience drift alerts and original transaction failures, and derive batch counts from constructed rows. Avoid sorting bounded cleanup reads and exercise recovery and completion guards through MySQL.
by Jonatan Sv...
J
Failed
30541
ab61763a Added verified newsletter recipient preparation ref https://linear.app/ghost/issue/BER-3927/verify-email-recipients-row-count-after-batch-creation Recover uncertain batch commits under stable IDs, account for candidate exclusions, and verify persisted recipients before freezing preparation. Rebuild only incomplete pending work and check persisted batch status before completing new emails; preserve the legacy path.
by Jonatan Sv...
J
Previous
Next