Overview - Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
30481
001eb54c Fixed post preview readiness and stale data no ref Preview actions must reflect the just-saved post and a current newsletter. Validating API responses and gating cached data behind readiness and error states prevents stale or malformed data from reaching users.
by Steve Larson
Failed
30481
001eb54c Fixed post preview readiness and stale data no ref Preview actions must reflect the just-saved post and a current newsletter. Validating API responses and gating cached data behind readiness and error states prevents stale or malformed data from reaching users.
by Steve Larson
Succeeded
30481
a9cff038 Fixed the preview's save gate and newsletter identity The gate that holds the preview back until the caller's save resolves was reading a ref that is only refreshed after commit, so a caller that passes the save conditionally — the natural shape, since only a dirty post needs saving — handed it `undefined` on the very render that opens the modal: the save never ran and the preview showed the server's stale copy. It reads the prop now; the ref exists only to keep the effect from re-running when the callback's identity changes. The post's newsletter is also what its email renders as, so the modal now looks it up when it has left the active list, instead of the From line and the test send quietly falling back to the first active newsletter while the preview request used the post's. The test for the save gate sampled the DOM after effects had flushed, so it passed against the bug it was meant to catch; it now watches for any preview frame entering or leaving the page while the save is in flight.
by Steve Larson
Succeeded
30481
a9cff038 Fixed the preview's save gate and newsletter identity The gate that holds the preview back until the caller's save resolves was reading a ref that is only refreshed after commit, so a caller that passes the save conditionally — the natural shape, since only a dirty post needs saving — handed it `undefined` on the very render that opens the modal: the save never ran and the preview showed the server's stale copy. It reads the prop now; the ref exists only to keep the effect from re-running when the callback's identity changes. The post's newsletter is also what its email renders as, so the modal now looks it up when it has left the active list, instead of the From line and the test send quietly falling back to the first active newsletter while the preview request used the post's. The test for the save gate sampled the DOM after effects had flushed, so it passed against the bug it was meant to catch; it now watches for any preview frame entering or leaving the page while the save is in flight.
by Steve Larson
Succeeded
30481
bb3b19cb Added the post preview components to the React editor The React editor can show a post's title and body but has no way to see how that post will actually reach readers, which is the last check most people make before publishing. These components cover both halves of that check — the site render and the newsletter render — as a self-contained modal: one audience selection drives the browser preview's query params and the email preview's request, and the test send goes to a single address for that same audience. They are not wired into the editor header yet; the header that opens them lands with the publish controls, so this ships the surface and its tests on their own. The email render is shown through a srcdoc iframe sandboxed without scripts or same-origin access, rather than written into the frame's document.
by Steve Larson
Succeeded
30481
bb3b19cb Added the post preview components to the React editor The React editor can show a post's title and body but has no way to see how that post will actually reach readers, which is the last check most people make before publishing. These components cover both halves of that check — the site render and the newsletter render — as a self-contained modal: one audience selection drives the browser preview's query params and the email preview's request, and the test send goes to a single address for that same audience. They are not wired into the editor header yet; the header that opens them lands with the publish controls, so this ships the surface and its tests on their own. The email render is shown through a srcdoc iframe sandboxed without scripts or same-origin access, rather than written into the frame's document.
by Steve Larson