TryGhost
OSS
Ghost
Fixed lazy URL service wrongly disowning posts in collection routes ref https://linear.app/ghost/issue/HKG-1875 - in compare mode the lazy URL service reported ownsResource false for posts the eager service owned, surfacing as LAZY_URL_PARITY_MISMATCH - the collection controller hands each rendered post to ownsResource to drop posts a higher-priority collection owns; the lazy service decides ownership by evaluating the base filter status:published+type:post against the resource, but the Content API serializer strips both status and type from public posts, so the filter never matched and every candidate post was disowned and removed from the collection - the eager service is unaffected: it owns by cache id membership (hasId), with the base filter applied once at fetch against full models, so it never re-evaluates the filter per call - the controller already restored type; restore status: 'published' as well, which is always correct because collections only ever load published posts. Restoring the stripped column keeps the base filter fully enforced rather than relaxing it, preserving parity with eager
nx run ghost:test:integration
Sign in / Sign up
Open main menu
Succeeded
CI Pipeline Execution
nx run ghost:test:integration
Click to copy
Linux
4 CPU cores
read-write
access token used
99a25f11
29008