TryGhostOSS
    Ghost
    Moved gift-link verification into the posts/pages Content API ref https://github.com/TryGhost/Ghost/pull/29064 - the entry controller previously verified gift tokens itself and re-read the entry as a paid-member shim, giving the frontend gift-service knowledge through the proxy seam and costing a second lookup per gift view - the frontend now passes the raw ?gift token through the single entry lookup as read context; the posts/pages read endpoints resolve it, verify it against the entry being read and unlock its gated content via the same shim previews use, or reject with INVALID_GIFT_TOKEN for the frontend to strip-and-301 - the token resolves to its post id in generateCacheKeyData, before the response cache is consulted: unlocked variants are cached by resolved post id, revocations take effect immediately, and an unresolvable token can never share a cache key with a plain read - ?gift stays intentionally a site-frontend concern: the token travels as internal read context only, so the public Content API ignores the param
    nx run @tryghost/admin:build
Succeeded
CI Pipeline Execution

nx run @tryghost/admin:build

Click to copy
Linux
4 CPU cores
read-write access token used
88a6eb3929078
100%

Cache hits

9 of 9 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

9 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools