TryGhostOSS
    Ghost
    Changed route settings FileStore to persist the original YAML - we decided the store should hold the user's original routes.yaml bytes rather than the parsed domain object as JSON: it keeps comments and formatting intact, makes the Pro migration a lossless byte copy with no Ghost-code dependency, and makes rollback trivially symmetric - RouteSettings now carries a readonly `yamlSource` — the verbatim YAML it was parsed from. parseRouteSettings requires the source alongside the raw structure so source and structure cannot drift at construction, and stores persist the bytes, never a re-serialised model - FileStore reads and writes only routes.yaml — the routes.json format and the yaml→json migration/rollback machinery are gone, so replace() is now just backup-then-atomic-write - the shared store contract test asserts yamlSource round-trips verbatim, so every future backend (e.g. the GCS store) inherits the check
    nx run ghost:test:legacy
Succeeded
CI Pipeline Execution

nx run ghost:test:legacy

Click to copy
Linux
4 CPU cores
read-write access token used
89210f0629269
93%

Cache hits

13 of 14 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

14 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools