Sourced from astro's releases.

astro@5.10.1

Patch Changes

• #13988 609044c Thanks @​ascorbic! - Fixes a bug in live collections that caused it to incorrectly complain about the collection being defined in the wrong file

• #13909 b258d86 Thanks @​isVivek99! - Fixes rendering of special boolean attributes for custom elements

• #13983 e718375 Thanks @​florian-lefebvre! - Fixes a case where the toolbar audit would incorrectly flag images processed by Astro in content collections documents

• #13999 f077b68 Thanks @​ascorbic! - Adds lastModified field to experimental live collection cache hints

  Live loaders can now set a lastModified field in the cache hints for entries and collections to indicate when the data was last modified. This is then available in the cacheHint field returned by getCollection and getEntry.

• #13987 08f34b1 Thanks @​ematipico! - Adds an informative message in dev mode when the CSP feature is enabled.

• #14005 82aad62 Thanks @​ematipico! - Fixes a bug where inline styles and scripts didn't work when CSP was enabled. Now when adding <styles> elements inside an Astro component, their hashes care correctly computed.

• #13985 0b4c641 Thanks @​jsparkdev! - Updates wrong link

astro@5.10.0

Minor Changes

• #13917 e615216 Thanks @​ascorbic! - Adds a new priority attribute for Astro's image components.

  This change introduces a new priority option for the <Image /> and <Picture /> components, which automatically sets the loading, decoding, and fetchpriority attributes to their optimal values for above-the-fold images which should be loaded immediately.

  It is a boolean prop, and you can use the shorthand syntax by simply adding priority as a prop to the <Image /> or <Picture /> component. When set, it will apply the following attributes:

  • loading="eager"
  • decoding="sync"
  • fetchpriority="high"

  The individual attributes can still be set manually if you need to customize your images further.

  By default, the Astro <Image /> component generates <img> tags that lazy-load their content by setting loading="lazy" and decoding="async". This improves performance by deferring the loading of images that are not immediately visible in the viewport, and gives the best scores in performance audits like Lighthouse.

  The new priority attribute will override those defaults and automatically add the best settings for your high-priority assets.

  This option was previously available for experimental responsive images, but now it is a standard feature for all images.

  Usage

  <Image src="/path/to/image.jpg" alt="An example image" priority />
  

  [!Note] You should only use the priority option for images that are critical to the initial rendering of the page, and ideally only one image per page. This is often an image identified as the LCP element when running Lighthouse tests. Using it for too many images will lead to performance issues, as it forces the browser to load those images immediately, potentially blocking the rendering of other content.

• #13917 e615216 Thanks @​ascorbic! - The responsive images feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.

... (truncated)

Sourced from astro's changelog.

5.10.1

Patch Changes

• #13988 609044c Thanks @​ascorbic! - Fixes a bug in live collections that caused it to incorrectly complain about the collection being defined in the wrong file

• #13909 b258d86 Thanks @​isVivek99! - Fixes rendering of special boolean attributes for custom elements

• #13983 e718375 Thanks @​florian-lefebvre! - Fixes a case where the toolbar audit would incorrectly flag images processed by Astro in content collections documents

• #13999 f077b68 Thanks @​ascorbic! - Adds lastModified field to experimental live collection cache hints

  Live loaders can now set a lastModified field in the cache hints for entries and collections to indicate when the data was last modified. This is then available in the cacheHint field returned by getCollection and getEntry.

• #13987 08f34b1 Thanks @​ematipico! - Adds an informative message in dev mode when the CSP feature is enabled.

• #14005 82aad62 Thanks @​ematipico! - Fixes a bug where inline styles and scripts didn't work when CSP was enabled. Now when adding <styles> elements inside an Astro component, their hashes care correctly computed.

• #13985 0b4c641 Thanks @​jsparkdev! - Updates wrong link

5.10.0

Minor Changes

• #13917 e615216 Thanks @​ascorbic! - Adds a new priority attribute for Astro's image components.

  This change introduces a new priority option for the <Image /> and <Picture /> components, which automatically sets the loading, decoding, and fetchpriority attributes to their optimal values for above-the-fold images which should be loaded immediately.

  It is a boolean prop, and you can use the shorthand syntax by simply adding priority as a prop to the <Image /> or <Picture /> component. When set, it will apply the following attributes:

  • loading="eager"
  • decoding="sync"
  • fetchpriority="high"

  The individual attributes can still be set manually if you need to customize your images further.

  By default, the Astro <Image /> component generates <img> tags that lazy-load their content by setting loading="lazy" and decoding="async". This improves performance by deferring the loading of images that are not immediately visible in the viewport, and gives the best scores in performance audits like Lighthouse.

  The new priority attribute will override those defaults and automatically add the best settings for your high-priority assets.

  This option was previously available for experimental responsive images, but now it is a standard feature for all images.

  Usage

  <Image src="/path/to/image.jpg" alt="An example image" priority />
  

  [!Note] You should only use the priority option for images that are critical to the initial rendering of the page, and ideally only one image per page. This is often an image identified as the LCP element when running Lighthouse tests. Using it for too many images will lead to performance issues, as it forces the browser to load those images immediately, potentially blocking the rendering of other content.

... (truncated)

• 339ee27 [ci] release (#13981)
• 08f34b1 fix: add info message in dev (#13987)
• 578a6d8 [ci] format
• 82aad62 fix(csp): hashes for head elements (#14005)
• f077b68 feat: add lastModified field to live collection cache hints (#13999)
• 609044c fix: loosen live collection stack parsing (#13988)
• 0b4c641 docs: update wrong link (#13985)
• e718375 fix: toolbar image audit in content collections (#13983)
• 97c3c8a [ci] format
• b258d86 added support to ignore custom elements which have htmlBooleanAt… (#13909)
• Additional commits viewable in compare view

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)