Skip to content

[pull] main from TryGhost:main - #1456

Merged
pull[bot] merged 1 commit into
code:mainfrom
TryGhost:main
Aug 31, 2026
Merged

[pull] main from TryGhost:main#1456
pull[bot] merged 1 commit into
code:mainfrom
TryGhost:main

Conversation

@pull

@pull pull Bot commented Aug 31, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

ref https://linear.app/ghost/issue/HKG-1972/migrate-update-checks-to-the-durable-jobs-interface

- The worker thread bought nothing here: its shim only re-initialised
  settings, permissions and email-address, which the main process
  already has before the jobs service starts, so the same
  UpdateCheckService body now runs in-process and the shim is deleted
  rather than ported.
- Both runs share a single UpdateCheckJob type because the boot and
  recurring identities always executed identical work; the dispatch-site
  "boot run queued" log keeps per-run attribution, and scheduled-vs-
  dispatched provenance belongs in the transport as a generic marker,
  not in per-job types.
- The randomized full-day cron and the forceUpdate-gated boot dispatch
  are preserved verbatim so production behavior is unchanged; failures
  now also reach the jobs service's structured logging and Sentry
  reporting, which the Bree path lacked. Verified against pro-infra
  that no Elastic alert keys on the legacy update-check log shape.
- Scheduling moved behind boot's try/catch like the other migrations,
  so a registration failure degrades to an error log instead of an
  unhandled rejection.
- The legacy integration test drove the deleted worker file directly,
  so it is replaced with one that dispatches through the real jobs
  service and additionally asserts next_update_check advances.
@pull pull Bot locked and limited conversation to collaborators Aug 31, 2026
@pull pull Bot added the ⤵️ pull label Aug 31, 2026
@pull
pull Bot merged commit 15a5653 into code:main Aug 31, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant