Bump astro from 5.14.4 to 5.14.6 in the astro-framework group

[dependabot]

Bumps the astro-framework group with 1 update: astro.

Updates astro from 5.14.4 to 5.14.6

Release notes

Sourced from astro's releases.

[email protected]

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 the maxAge property in cacheHint 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 supports tags and lastModified 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 missing rendered property to experimental live collections entry type

  Live 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.

[email protected]

Patch Changes

• #14525 4f55781 Thanks @​penx! - Fixes defineLiveCollection() types

• #14441 62ec8ea Thanks @​upsuper! - Updates redirect handling to be consistent across static and server output, aligning with the behavior of other adapters.

  Previously, the Node.js adapter used default HTML files with meta refresh tags when in static output. This often resulted in an extra flash of the page on redirect, while also not applying the proper status code for redirections. It's also likely less friendly to search engines.

  This update ensures that configured redirects are always handled as HTTP redirects regardless of output mode, and the default HTML files for the redirects are no longer generated in static output. It makes the Node.js adapter more consistent with the other official adapters.

... (truncated)

Changelog

Sourced from astro's changelog.

5.14.6

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 the maxAge property in cacheHint 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 supports tags and lastModified 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 missing rendered property to experimental live collections entry type

  Live 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.

5.14.5

Patch Changes

• #14525 4f55781 Thanks @​penx! - Fixes defineLiveCollection() types

• #14441 62ec8ea Thanks @​upsuper! - Updates redirect handling to be consistent across static and server output, aligning with the behavior of other adapters.

  Previously, the Node.js adapter used default HTML files with meta refresh tags when in static output. This often resulted in an extra flash of the page on redirect, while also not applying the proper status code for redirections. It's also likely less friendly to search engines.

... (truncated)

Commits

• 4f1afc3 [ci] release (#14551)
• 722bba0 Fix: add muted to html boolean attributes (#14562)
• 9f0601d [ci] format
• 6cdade4 fix: updates types for live collection entries (#14548)
• af801ca [ci] format
• 51ebe6a refactor(actions): plugin and virtual modules (#14538)
• adaaced chore: bump biome and errors (#14539)
• ef7af66 [ci] release (#14527)
• 62ec8ea feat(node): handle redirects dynamically in static mode (#14441)
• 4f55781 Update content.d.ts astro/loader => loaders (#14525)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
documentation	Error		Oct 20, 2025 9:35am

💡 Enable Vercel Agent with $100 free credit for automated AI reviews