TryGhost
OSS
Ghost
Added routes_hash continuity test for the activation bridge - getCurrentHash() is md5(JSON.stringify(...)) over the expanded settings, and route-settings.js hardcodes the hash of the expanded default routes ('3d180d52...'). That constant is the only hash value external consumers could compare against, so it must survive the switch from validate.js to parser + activation bridge — this test pins both paths to it - the existing equivalence tests use deepEqual, which is key-order-insensitive; JSON.stringify is not, so hash continuity was untested until now - byte-identical hashes for customized configs are not achievable: validate.js mutates the parsed YAML in place, so its output key order (and hash) depends on the order keys were written in the user's routes.yaml, which a normalized domain model cannot preserve. Customized sites will get a harmless one-time routes_hash re-sync when the read path switches — nothing reads routes_hash except the sync comparison itself - keeps the upcoming FileStore PR free of hash concerns: hashing stays in the service, computed over the bridge output
nx run ghost-monorepo:lint:boundaries
Sign in / Sign up
Open main menu
Succeeded
CI Pipeline Execution
nx run ghost-monorepo:lint:boundaries
Click to copy
Linux
4 CPU cores
read-write
access token used
b3e9874a
29191