Back to changelog

v2026.7.12-c9a7dae1
  • Developer Experience
  • Performance

Content caching you can actually control

Per-content cache settings with TTLs, cache tags and webhook delivery — wire b10cks straight into your CDN's invalidation instead of guessing at expiry times.

Fast sites cache aggressively; correct sites invalidate precisely. New content cache settings let you do both:

  • TTLs per content — choose how long delivery responses may be cached, per entry or inherited down the tree
  • Cache tags — tag entries and let your CDN or app invalidate exactly the pages a change affects
  • Webhook delivery — publishes and unpublishes notify your infrastructure the moment they happen, with the affected tags in the payload

Alongside it, the delivery API keeps getting leaner: heavy search columns stay out of read queries and token lookups got a dedicated unique index. The same release also brought default values from block definitions, fuzzy search in the content tree, and per-content child sorting.