Overview - Ghost

GhostWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

Ghost

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

GhostWorkspace

Agents
Replay
VCS
Self-Healing

Average execution time

8m 7s

2197 CI pipeline executions

Computation time saved

28d 13h

Cache hit rate

86%

Protect cache integrity with sandboxing

Time to Green

48m 16s

Was 58m 41s, improved by 18%

Succeeded
main
c2c91c7b Fixed migration checks treating moved migrations as new (#31632) no ref The migration integrity check and the release script's minor-bump detection both diffed only the migrations directory. Git can only pair a rename when both paths are in the diff, so moving that directory dropped the old paths and reported every existing migration as newly added: the integrity check failed on already-shipped folders, and the release script would force a minor bump. Both now diff the whole tree with rename detection. A rename still counts as a new migration unless its path within the versions directory is unchanged, so moving the whole directory adds nothing, while moving a file between version folders or into the directory from elsewhere is still caught.
by Austin Bur...
A
Succeeded
main
7bf2b147 Changed Koenig demo to deploy via GitHub Pages Actions (#31640) no ref Publishing to a gh-pages branch added a full built bundle to the Ghost repo's history on every deploy, which every full clone then downloads, and it needed contents: write on a job that runs third-party build steps. Deploying through upload-pages-artifact/deploy-pages keeps the output out of git, narrows the deploy job to pages/id-token, and drops the third-party peaceiris action. The custom domain moves to repo settings, so the CNAME step is no longer needed.
by Austin Bur...
Succeeded
main
7bf2b147 Changed Koenig demo to deploy via GitHub Pages Actions (#31640) no ref Publishing to a gh-pages branch added a full built bundle to the Ghost repo's history on every deploy, which every full clone then downloads, and it needed contents: write on a job that runs third-party build steps. Deploying through upload-pages-artifact/deploy-pages keeps the output out of git, narrows the deploy job to pages/id-token, and drops the third-party peaceiris action. The custom domain moves to repo settings, so the CNAME step is no longer needed.
by Austin Bur...
A
Succeeded
main
7bf2b147 Changed Koenig demo to deploy via GitHub Pages Actions (#31640) no ref Publishing to a gh-pages branch added a full built bundle to the Ghost repo's history on every deploy, which every full clone then downloads, and it needed contents: write on a job that runs third-party build steps. Deploying through upload-pages-artifact/deploy-pages keeps the output out of git, narrows the deploy job to pages/id-token, and drops the third-party peaceiris action. The custom domain moves to repo settings, so the CNAME step is no longer needed.
by Austin Bur...
Succeeded
31640
29709f8c Changed Koenig demo to deploy via GitHub Pages Actions no ref Publishing to a gh-pages branch adds a full built bundle to the Ghost repo's history on every deploy, which every full clone then downloads, and it needs contents: write on a job that runs third-party build steps. Deploying through upload-pages-artifact/deploy-pages keeps the output out of git, narrows the deploy job to pages/id-token, and drops the third-party peaceiris action. The custom domain moves to repo settings, so the CNAME step is no longer needed.
by Austin Bur...
A
Succeeded
31630
f160e101 Moved the Ghost package from ghost/core to ghost no ref The ghost package lived at ghost/core and kept its server code in a nested core/ directory, so every server path read ghost/core/core/... Moving the package root up one level removes the doubled segment without touching the package's internal layout: the release tarball, Ghost-CLI installs, the paths:* config defaults and any self-hoster overrides keep their core/ paths. Only references that cross the package boundary change: monorepo paths in CI, Docker, compose, nx inputs, app configs and docs, plus the few relative paths from inside the package back out to the repo root. The asset build scripts now locate the package from their own location rather than matching the cwd name, which would otherwise also match a repo checkout named ghost. The root logs ignore rule now ignores contents rather than every logs/ directory, so the tracked content/logs README is no longer inside an ignored directory; staging its rename failed otherwise.
by Austin Bur...
A
Succeeded
main
c2c91c7b Fixed migration checks treating moved migrations as new (#31632) no ref The migration integrity check and the release script's minor-bump detection both diffed only the migrations directory. Git can only pair a rename when both paths are in the diff, so moving that directory dropped the old paths and reported every existing migration as newly added: the integrity check failed on already-shipped folders, and the release script would force a minor bump. Both now diff the whole tree with rename detection. A rename still counts as a new migration unless its path within the versions directory is unchanged, so moving the whole directory adds nothing, while moving a file between version folders or into the directory from elsewhere is still caught.
by Austin Bur...
A
Succeeded
main
c2c91c7b Fixed migration checks treating moved migrations as new (#31632) no ref The migration integrity check and the release script's minor-bump detection both diffed only the migrations directory. Git can only pair a rename when both paths are in the diff, so moving that directory dropped the old paths and reported every existing migration as newly added: the integrity check failed on already-shipped folders, and the release script would force a minor bump. Both now diff the whole tree with rename detection. A rename still counts as a new migration unless its path within the versions directory is unchanged, so moving the whole directory adds nothing, while moving a file between version folders or into the directory from elsewhere is still caught.
by Austin Bur...
Succeeded
31632
fcd2b121 Fixed migration checks treating moved migrations as new no ref The migration integrity check and the release script's minor-bump detection both diffed only the migrations directory. Git can only pair a rename when both paths are in the diff, so any move of that directory dropped the old paths and reported every existing migration as newly added: the integrity check failed on already-shipped folders, and the release script would force a minor bump. Both now diff the whole tree with rename detection. A rename still counts as a new migration unless its path within the versions directory is unchanged, so moving the whole directory adds nothing while moving a file between version folders, or into the directory from elsewhere, is still caught.
by Austin Bur...
A
Succeeded
31630
d040582e Moved the Ghost package from ghost/core to ghost no ref The ghost package lived at ghost/core and kept its server code in a nested core/ directory, so every server path read ghost/core/core/... Moving the package root up one level removes the doubled segment without touching the package's internal layout: the release tarball, Ghost-CLI installs, the paths:* config defaults and any self-hoster overrides keep their core/ paths. Only references that cross the package boundary change: monorepo paths in CI, Docker, compose, nx inputs, app configs and docs, plus the few relative paths from inside the package back out to the repo root. The asset build scripts now locate the package from their own location rather than matching the cwd name, which would otherwise also match a repo checkout named ghost. The root logs ignore rule now ignores contents rather than every logs/ directory, so the tracked content/logs README is no longer inside an ignored directory; staging its rename failed otherwise.
by Austin Bur...
A
Succeeded
31632
d5fc3f87 Fixed migration checks treating moved migrations as new no ref The migration integrity check and the release script's minor-bump detection both diffed only the migrations directory. Git can only pair a rename when both paths are in the diff, so any move of that directory dropped the old paths and reported every existing migration as newly added: the integrity check failed on already-shipped folders, and the release script would force a minor bump. Both now diff the whole tree with rename detection and filter to the migrations directory afterwards.
by Austin Bur...
A
Succeeded
31630
fa3799f1 Moved the Ghost package from ghost/core to ghost no ref The ghost package lived at ghost/core and kept its server code in a nested core/ directory, so every server path read ghost/core/core/... Moving the package root up one level removes the doubled segment without touching the package's internal layout: the release tarball, Ghost-CLI installs, the paths:* config defaults and any self-hoster overrides keep their core/ paths. Only references that cross the package boundary change: monorepo paths in CI, Docker, compose, nx inputs, app configs and docs, plus the few relative paths from inside the package back out to the repo root. The asset build scripts now locate the package from their own location rather than matching the cwd name, which would otherwise also match a repo checkout named ghost. The root logs ignore rule now ignores contents rather than every logs/ directory, so the tracked content/logs README is no longer inside an ignored directory; staging its rename failed otherwise.
by Austin Bur...
A
Succeeded
main
32b94779 🐛 Fixed non-object config values wiping out nested config defaults (#31629) ref https://forum.ghost.org/t/edit-is-not-redirecting-toward-backoffice-anymore/63947 Since the frozen config tree, config is built from `nconf.get()`, which merges whole stores - so any non-object value (string, number, null, array) in a higher-priority source replaces the object below it entirely, taking every nested default with it. Before the tree, every read went through nconf per key, which looks past a non-object to the stores below it, so such values were silent no-ops. The tree is now merged with the same rule, so sub-key reads match what they returned before, and a warning names the ignored key and the source it came from. For every shipped env config the result is identical to `nconf.get()`. Prototype keys are skipped during the merge. Reported with Cloudron's `"admin": "https://..."`, which dropped the `admin` defaults: `/edit` stopped redirecting to Admin and the session cookie lost its max age.
by Austin Bur...
Succeeded
main
32b94779 🐛 Fixed non-object config values wiping out nested config defaults (#31629) ref https://forum.ghost.org/t/edit-is-not-redirecting-toward-backoffice-anymore/63947 Since the frozen config tree, config is built from `nconf.get()`, which merges whole stores - so any non-object value (string, number, null, array) in a higher-priority source replaces the object below it entirely, taking every nested default with it. Before the tree, every read went through nconf per key, which looks past a non-object to the stores below it, so such values were silent no-ops. The tree is now merged with the same rule, so sub-key reads match what they returned before, and a warning names the ignored key and the source it came from. For every shipped env config the result is identical to `nconf.get()`. Prototype keys are skipped during the merge. Reported with Cloudron's `"admin": "https://..."`, which dropped the `admin` defaults: `/edit` stopped redirecting to Admin and the session cookie lost its max age.
by Austin Bur...
A
Succeeded
31629
c7654b69 🐛 Fixed non-object config values wiping out nested config defaults ref https://forum.ghost.org/t/edit-is-not-redirecting-toward-backoffice-anymore/63947 Since the frozen config tree, config is built from `nconf.get()`, which merges whole stores - so any non-object value (string, number, null, array) in a higher-priority source replaces the object below it entirely, taking every nested default with it. Before the tree, every read went through nconf per key, which looks past a non-object to the stores below it, so such values were silent no-ops. The tree is now merged with the same rule, so sub-key reads match what they returned before, and a warning names the ignored key and the source it came from. For every shipped env config the result is identical to `nconf.get()`. Reported with Cloudron's `"admin": "https://..."`, which dropped the `admin` defaults: `/edit` stopped redirecting to Admin and the session cookie lost its max age.
by Austin Bur...
A
Succeeded
31629
ff03a910 🐛 Fixed non-object config values wiping out nested config defaults ref https://forum.ghost.org/t/edit-is-not-redirecting-toward-backoffice-anymore/63947 Since the frozen config tree, config is built from `nconf.get()`, which merges whole stores - so any non-object value (string, number, null, array) in a higher-priority source replaces the object below it entirely, taking every nested default with it. Before the tree, every read went through nconf per key, which looks past a non-object to the stores below it, so such values were silent no-ops. The tree is now merged with the same rule, so sub-key reads match what they returned before, and a warning names the ignored key and the source it came from. For every shipped env config the result is identical to `nconf.get()`. Reported with Cloudron's `"admin": "https://..."`, which dropped the `admin` defaults: `/edit` stopped redirecting to Admin and the session cookie lost its max age.
by Austin Bur...
A
Succeeded
31629
949c0f3d 🐛 Fixed /edit redirects 404ing when a config value replaces an object ref https://forum.ghost.org/t/edit-is-not-redirecting-toward-backoffice-anymore/63947 Since the frozen config tree, config is built from `nconf.get()`, which merges whole stores - so a non-object in a site's config replaces the object below it entirely. Cloudron writes `"admin": "https://..."`, which dropped every `admin` default: `/edit` stopped redirecting to Admin and the session cookie lost its max age. Before the tree, every read went through nconf per key, which looks past a non-object to the stores below it, so that config was a silent no-op. The tree is now merged with the same rule, so sub-key reads match what they returned before, and a warning names the ignored key and the file it came from. For every shipped env config the result is identical to `nconf.get()`.
by Austin Bur...
A
Succeeded
31566
76ebde47 Merge branch 'main' into claude/ghost-core-rebalancing-tests-37aa94
by Austin Bur...
A
Succeeded
31566
38b78516 Removed workspace builds from Ghost core test dependencies no ref Ghost core's test workers already resolve workspace packages to src/ through the `source` export condition, so the ^build step nx ran before every test target only fed one consumer: the DB suites' globalSetup, which builds the template database in vitest's main process where ssr.resolve.conditions doesn't apply. Passing --conditions=source through NODE_OPTIONS covers that process too, so the test targets now depend only on build:assets. With nothing built needed, the acceptance and legacy jobs install just ghost's dependency subgraph plus the root (for nx), which roughly halves the packages linked and proves the suites don't lean on anything outside it.
by Austin Bur...
A
Succeeded
main
48d0d9e9 Removed dtrace from dependency graph (#31560) no ref - pulled in optionally via bunyan, does nothing on any OS outside of OSX Intel, and generates lots of build-time noise - remove via ignoredOptionalDeps to remove its nan dependency as well
by Austin Bur...
A