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

7m 29s

1996 CI pipeline executions

Computation time saved

29d 12h

Cache hit rate

83%

Protect cache integrity with sandboxing

Time to Green

38m 15s

Was 45m 20s, improved by 16%

Succeeded
31747
a0123add Fixed knex-migrator scripts failing until workspace packages are built no ref `pnpm reset:db`, `migrate:db`, `rollback:db` and `knex-migrator` loaded workspace packages from `build/`, which only exists once `pnpm dev` has built them for Admin. Ghost itself runs from source (`--conditions=source --import=tsx`), so in a new worktree these scripts failed with MODULE_NOT_FOUND for `@tryghost/limit-service/build/index.js`, and elsewhere they ran the build from the last `pnpm dev` start rather than the current source. The flags go in NODE_OPTIONS because the `knex-migrator` bin runs each subcommand as a separate process, which doesn't inherit Node's command-line flags. `env` sets them on knex-migrator alone: set on `pnpm exec`, they'd also reach the lifecycle scripts of an automatic install, where `--import=tsx` doesn't resolve.
by Steve Larson
S
Succeeded
31747
933600c7 Fixed knex-migrator scripts failing until workspace packages are built no ref In a freshly bootstrapped worktree, `pnpm reset:db`, `migrate:db`, `rollback:db` and `knex-migrator` failed with MODULE_NOT_FOUND for `@tryghost/limit-service/build/index.js`. Workspace packages export `src/` under the `source` condition and `build/` otherwise. `pnpm dev` and `pnpm reset:data` run Ghost with `--conditions=source --import=tsx`, so nothing builds those packages, but knex-migrator loaded Ghost with the default conditions. The flags go in NODE_OPTIONS rather than on a `node` command because the `knex-migrator` bin runs each subcommand (`init`, `migrate`, ...) as a separate process, which doesn't inherit Node's command-line flags. `pnpm exec` appends its own NODE_OPTIONS hook after these.
by Steve Larson
S