TryGhostOSS
    Ghost
    Fixed strict route settings validation rejecting legacy-shaped YAML values - a fleet audit of 41,346 Ghost Pro routes.yaml files found 97 that the strict parser rejects but legacy validate.js accepts; 48 of them are pure value-shape mismatches with unambiguous intent, which the parser now accepts: digit-only string limits (limit: "100") coerce to numbers, and empty YAML values (filter:, template: -> null) are treated as unset - matching what YAML authors mean and what the legacy validator did - the gate stays strict where intent is ambiguous or the construct is deliberately forbidden: limit: banana, unknown controllers, colon paths, and template-less route objects still fail, so the remaining 49 sites stay on the legacy validation fallback until fixed per-site - shrinking the fallback population is a precondition for retiring the legacy validator modules and for flipping sites to the remote store
    nx run ghost:test:ci:integration
Succeeded
CI Pipeline Execution

nx run ghost:test:ci:integration

Click to copy
Linux
4 CPU cores
read-write access token used
044c85e529330
94%

Cache hits

15 of 16 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

16 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools