Sourced from astro's releases.

astro@5.11.2

Patch Changes

• #14064 2eb77d8 Thanks @​jp-knj! - Allows using tsconfig compilerOptions.paths without setting compilerOptions.baseUrl

• #14068 10189c0 Thanks @​jsparkdev! - Fixes the incorrect CSS import path shown in the terminal message during Tailwind integration setup.

Sourced from astro's changelog.

5.11.2

Patch Changes

• #14064 2eb77d8 Thanks @​jp-knj! - Allows using tsconfig compilerOptions.paths without setting compilerOptions.baseUrl

• #14068 10189c0 Thanks @​jsparkdev! - Fixes the incorrect CSS import path shown in the terminal message during Tailwind integration setup.

5.11.1

Patch Changes

• #14045 3276b79 Thanks @​ghubo! - Fixes a problem where importing animated .avif files returns a NoImageMetadata error.

• #14041 0c4d5f8 Thanks @​dixslyf! - Fixes a <ClientRouter /> bug where the fallback view transition animations when exiting a page ran too early for browsers that do not support the View Transition API. This bug prevented event.viewTransition?.skipTransition() from skipping the page exit animation when used in an astro:before-swap event hook.

5.11.0

Minor Changes

• #13972 db8f8be Thanks @​ematipico! - Updates the NodeApp.match() function in the Adapter API to accept a second, optional parameter to allow adapter authors to add headers to static, prerendered pages.

  NodeApp.match(request) currently checks whether there is a route that matches the given Request. If there is a prerendered route, the function returns undefined, because static routes are already rendered and their headers cannot be updated.

  When the new, optional boolean parameter is passed (e.g. NodeApp.match(request, true)), Astro will return the first matched route, even when it's a prerendered route. This allows your adapter to now access static routes and provides the opportunity to set headers for these pages, for example, to implement a Content Security Policy (CSP).

Patch Changes

• #14029 42562f9 Thanks @​ematipico! - Fixes a bug where server islands wouldn't be correctly rendered when they are rendered inside fragments.

  Now the following examples work as expected:

  ---
  import { Cart } from '../components/Cart.astro';
  ---
  <>
  <Cart server:defer />
  </>
  <Fragment slot="rest">
  <Cart server:defer>
  <div slot="fallback">Not working</div>
  </Cart>
  </Fragment>

... (truncated)

• 5ec5088 [ci] release (#14072)
• c2e16b3 [ci] format
• 2eb77d8 fix(astro): drop baseUrl requirement for ts-paths (#14064)
• 2dbf999 [ci] format
• 10189c0 fix: Fix incorrect CSS import path in Tailwind integration setup (#14068)
• See full diff 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)