Platform 2026.05.19
On production sites
This release gives you more control over asset caching and page policies, and makes large deploys and related records faster.
Set cache rules on your assets
Use the new cache_control argument on the admin_assets_create and admin_asset_update mutations to set how long CDNs and browsers may cache an asset, for example max-age=31536000, public.
Attach authorization policies to a page by name
The admin_page_create and admin_page_update mutations now accept an authorization_policies argument. Use the same policy names you write in Liquid front matter, such as page_policy or modules/my_module/page_policy. You can combine names with the existing authorization_policy_ids. Every name must match an existing authorization policy.
Deploy very large sites more smoothly
Pages now load in batches during a deploy. This gives better support for very large deploys, especially those with pages created by static site generators.
Faster related_records
related_records now runs up to 4x faster.
Deprecation: the url argument in admin_assets_create
The url argument is now ignored. Asset URLs come from the asset name and your instance's CDN. Upload the file with admin_assets_presign_urls first, then call admin_assets_create without url. The argument will be removed in a future release.
Also in this release
- Asset URLs from the
asset_urlandasset_pathfilters now change together whenever any asset is updated, so cached copies stay consistent insites-cli duplicateis faster when an instance has many assets- If a clone fails to export, it now ends with a clear
failedstatus and message, soinsites-clistops waiting instead of hanging