Skip to content

Moved Ghost update's analytics check into release qualification (S7) #414

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
acburdine merged 1 commit into from
Oct 20, 2026
Merged

Moved Ghost update's analytics check into release qualification (S7) #414

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 3 additions & 13 deletions docs/ghost-cli-replacement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Linear](https://linear.app/ghost/issue/PLA-412).
| --- | --- | --- |
| Tagged single-site production | S5e production import, S12 qualification | Existing image self-update, local import, backup and restore |
| Several sites behind shared Caddy | S13 | Existing backup/restore and released-main migration |
| Admin-driven Ghost upgrades | S7 analytics acceptance, S9 core adapter/API, S10 Admin | Existing `update` and upgrade supervisor; S9 before S10; S13 integration if shipped |
| Admin-driven Ghost upgrades | S9 core adapter/API, S10 Admin | Existing `update` and upgrade supervisor; S9 before S10; S13 integration if shipped |
| Later extensions | S11 file secrets, S14 service references, S15 nightly transitions, S16 Redis | See each step |

Qualify production on Linux with rootful Docker Engine. Local qualification also covers
Expand Down Expand Up @@ -43,17 +43,6 @@ its recovery, and the admin domain in CI; the cross-host move is run by hand. Th
`scripts/migrate.sh`; S12 must not merge `next-docker` into `main` before these
scenarios pass.

### S7 — Host-driven Ghost upgrades

Repo: ghost-docker. `./ghost-docker update [version|latest]` moves a site within its
Ghost major, through the update executor self-update shares (`src/update.ts`), as
[install.md](install.md#update) describes. `tests/e2e/ghost-update.sh` covers an
upgrade across real migrations, a target that fails after startup, and refusals in
CI. Remaining:

Acceptance on a site with analytics: the update reruns Tinybird sync from the new
image and the deploy succeeds. It needs a Tinybird login, so it is run by hand.

### S9 — Ghost upgrade adapter and Admin API

Repo: Ghost core. Deps: the supervisor's protocol ([upgrade-supervisor.md](upgrade-supervisor.md)).
Expand Down Expand Up @@ -113,7 +102,8 @@ Gates the first stable tag and merging `next-docker` into `main`. Include the la
on Linux, macOS and WSL2. Consolidate CI and qualify the actual minimum supported tools
and image versions. Run fresh local/production install, optional-service variants, CLI
migration, legacy stack update, Ghost upgrade/recovery, supervisor/Admin, and restore
scenarios. Before merging, pin the migration tests' `GD_RELEASED_MAIN`
scenarios. On a site with analytics, `update` must rerun Tinybird sync from the new
image and the deploy must succeed; it needs a Tinybird login, so it is run by hand. Before merging, pin the migration tests' `GD_RELEASED_MAIN`
(default `origin/main`, in `manager/test/site.ts`, `tests/e2e/migrate-main.sh` and
the manager CI job) to `main`'s last commit, and rerun them. Include Linux runtime tests and macOS-compatible shell/configuration checks.
Record the [compatibility baseline](architecture.md#compatibility): the exact metadata
Expand Down
Loading