Patch Changes
-
#14562
722bba0
Thanks @erbierc! - Fixes a bug where the behavior of the "muted" HTML attribute was inconsistent with that of other attributes. -
#14538
51ebe6a
Thanks @florian-lefebvre! - Improves how Actions are implemented -
#14548
6cdade4
Thanks @ascorbic! - Removes support for themaxAge
property incacheHint
objects returned by live loaders.⚠️ Breaking change for experimental live content collections only
Feedback showed that this did not make sense to set at the loader level, since the loader does not know how long each individual entry should be cached for.
If your live loader returns cache hints with
maxAge
, you need to remove this property:return { entries: [...], cacheHint: { tags: ['my-tag'], - maxAge: 60, lastModified: new Date(), }, };
The
cacheHint
object now only supportstags
andlastModified
properties. If you want to set the max age for a page, you can set the headers manually:--- Astro.headers.set('cdn-cache-control', 'max-age=3600'); ---
-
#14548
6cdade4
Thanks @ascorbic! - Adds missingrendered
property to experimental live collections entry typeLive collections support a
rendered
property that allows you to provide pre-rendered HTML for each entry. While this property was documented and implemented, it was missing from the TypeScript types. This could lead to type errors when trying to use it in a TypeScript project.No changes to your project code are necessary. You can continue to use the
rendered
property as before, and it will no longer produce TypeScript errors.