Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
29269
dd43762e 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
by Princi Ver...
Succeeded
29269
e093cda3 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
by Princi Ver...
Succeeded
29269
e7ca2a55 Changed route settings FileStore to persist the original YAML verbatim - 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
by Princi Ver...
Succeeded
29269
56e8dbed Added FileStore adapter for storing route settings on local disk - first implementation of the RouteSettingsStore contract: route settings storage now sits behind one boundary, with FileStore as the local-disk backend. A GCS store will be added in next commits. - we now store the parsed domain object (as routes.json) instead of raw YAML, so the stored shape is the same for every backend and round-trips losslessly; existing routes.yaml files stay readable and migrate with a timestamped backup on first write - the empty state returns the bundled defaults from memory instead of seeding a file on boot, because a store that writes on read cannot work on read-only filesystems or object storage - corrupt or unreadable files throw instead of falling back to defaults so a broken settings folder can never silently replace a site's routing config
by Princi Ver...