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

12m 24s

591 CI pipeline executions

Computation time saved

15d 57m

Cache hit rate

90%

Protect cache integrity with sandboxing

Time to Green

56m 47s

Was 1h 9m, improved by 19%

Succeeded
30466
1930c0ab Added Node 24 to the supported engines range no ref Ghost should run on Node 24, but nothing about shipping on it has to change to get there. This declares 24 as supported and leaves 22.23.1 as the default everywhere it is one: devEngines, .nvmrc, .node-version, CI's NODE_VERSION and all three Dockerfiles. Pro keeps building and running the same image. The unit, legacy and acceptance matrices have run on 24 for a while and stayed green through a bug that stopped Ghost booting at all — an ESM/CJS require race on `got` that only fired during init migrations. Those suites stop at module level, so full boot is the coverage that was missing. Ghost-CLI's clean-install scenario is the cheapest place to get it: it installs this build's tarball and starts it, so it now runs on every Node line `engines` claims, off the same list the other matrices use. The latest-release scenario stays on the default. It upgrades from the newest Ghost on npm, and that release's own `engines` decides which Node versions can install it — it can join the full list once a published release supports 24. The debug-log artifact name carries the Node version as well as the scenario, since the clean-install legs would otherwise collide on upload. engines.cli is unchanged: the ^1.29.1 minimum is already above the Ghost-CLI release that added Node 24 support. The renovate @types/node cap also stays at <23, since it tracks the Node version we develop and build against, which is still 22. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Austin Bur...
Succeeded
30466
af089c20 Added Node 24 to the supported engines range no ref Ghost should run on Node 24, but nothing about shipping on it has to change to get there. This declares 24 as supported and leaves 22.23.1 as the default everywhere it is one: devEngines, .nvmrc, .node-version, CI's NODE_VERSION and all three Dockerfiles. Pro keeps building and running the same image. The unit, legacy and acceptance matrices have run on 24 for a while and stayed green through a bug that stopped Ghost booting at all — an ESM/CJS require race on `got` that only fired during init migrations. Those suites stop at module level, so full boot is the coverage that was missing. Ghost-CLI's clean-install scenario is the cheapest place to get it: it installs this build's tarball and starts it, so it now runs on every Node line `engines` claims, off the same list the other matrices use. The latest-release scenario stays on the default. It upgrades from the newest Ghost on npm, and that release's own `engines` decides which Node versions can install it — it can join the full list once a published release supports 24. engines.cli is unchanged: the ^1.29.1 minimum is already above the Ghost-CLI release that added Node 24 support. The renovate @types/node cap also stays at <23, since it tracks the Node version we develop and build against, which is still 22. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Austin Bur...