Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
29523
cceb9e6a 🐛 Fixed custom routes with :param paths being rejected on upload ref https://linear.app/ghost/issue/HKG-1940/ - the new route-settings validator rejected `:param` in every path, but route and collection keys are mounted on Express verbatim — nothing rewrites `{param}` to `:param` for them the way it does for permalinks and taxonomies - so `/author/:slug/` is a working wildcard route on live sites, and the error's suggested `/author/{slug}/` would mount a literal, unreachable path — the "fix" it recommended would have silently killed the route - legacy validate.js only ever checked `/:\w+` on collection permalinks and taxonomy values, so this restores parity there and keeps the tightening where legacy also tightened; permalinks and taxonomies still reject :param - also accepts `%s` as a data shorthand slug: fetch-data substitutes it with the request's slug param on channel routes and collections, which is what makes a wildcard route serve a different resource per request. There is no static slug that could replace it - 10 files in the Pro fleet depend on these two forms and now validate without needing edits; uploads accept them again, as they did before the migration
by Princi Ver...