AstroEco is Releasing…

Display your GitHub releases using astro-loader-github-releases

@astrojs/netlify

withastro/astro

v6.4.0 Jun 17

Minor Changes

#13952 de82ef2 Thanks @ematipico! - Adds support for the experimental static headers Astro feature.

When the feature is enabled via option experimentalStaticHeaders, and experimental Content Security Policy is enabled, the adapter will generate Response headers for static pages, which allows support for CSP directives that are not supported inside a <meta> tag (e.g. frame-ancestors).
```
import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify';

export default defineConfig({
  adapter: netlify({
    experimentalStaticHeaders: true,
  }),
  experimental: {
    cps: true,
  },
});
```

Patch Changes

Updated dependencies [de82ef2, de82ef2, de82ef2]:
- @astrojs/underscore-redirects@1.0.0

@astrojs/underscore-redirects

withastro/astro

v1.0.0 Jun 17

Major Changes

#13952 de82ef2 Thanks @ematipico! - - The type Redirects has been renamed to HostRoutes.
- RouteDefinition.target is now optional
- RouteDefinition.weight is now optional
- Redirects.print has been removed. Now you need to pass Redirects type to the print function
```
- redirects.print()
+ import { printAsRedirects } from "@astrojs/underscore-redirects"
+ printAsRedirects(redirects)
```

Minor Changes

#13952 de82ef2 Thanks @ematipico! - Adds a new method called createHostedRouteDefinition, which returns a HostRoute type from a IntegrationResolvedRoute.
#13952 de82ef2 Thanks @ematipico! - Adds a new method called printAsRedirects to print HostRoutes as redirects for the _redirects file.

@astrojs/cloudflare

withastro/astro

v2.5.5 Jun 17

Patch Changes

#13930 acb9b30 Thanks @alexanderniebuhr! - Fixes an issue where setting values for Astro.response resulted in a Cloudflare runtime exception.
Updated dependencies [de82ef2, de82ef2, de82ef2]:
- @astrojs/underscore-redirects@1.0.0

astro

withastro/astro

v5.9.4 Jun 17

Patch Changes

#13951 7eb88f1 Thanks @ascorbic! - Fixes a issue that caused errors when using an adapter-provided session driver with custom options
#13953 448bddc Thanks @zaitovalisher! - Fixes a bug where quotes were not added to the 'strict-dynamic' CSP directive

@astrojs/starlight

withastro/starlight

v0.34.4 Jun 13

Patch Changes

#3205 95d124a Thanks @sgalcheung! - Fixes an issue preventing to use the <StarlightPage> component when the docs content collection that Starlight uses does not exist.
#3206 e6ea584 Thanks @HiDeoo! - Fixes a text selection issue for heading with a clickable anchor link when using double click to select text in Chrome and Safari.
#3233 3064c40 Thanks @torn4dom4n! - Updates Vietnamese UI translations.
#3248 16c1239 Thanks @HiDeoo! - Prevents icons in the <Card> component from being shrunk in some narrow viewports.
#3225 21b93b8 Thanks @randomguy-2650! - Updates German UI translations

astro

withastro/astro

v5.9.3 Jun 13

Patch Changes

#13923 a9ac5ed Thanks @ematipico! - BREAKING CHANGE to the experimental Content Security Policy (CSP) only

Changes the behavior of experimental Content Security Policy (CSP) to now serve hashes differently depending on whether or not a page is prerendered:
- Via the <meta> element for static pages.
- Via the Response header content-security-policy for on-demand rendered pages.
This new strategy allows you to add CSP content that is not supported in a <meta> element (e.g. report-uri, frame-ancestors, and sandbox directives) to on-demand rendered pages.

No change to your project code is required as this is an implementation detail. However, this will result in a different HTML output for pages that are rendered on demand. Please check your production site to verify that CSP is working as intended.

To keep up to date with this developing feature, or to leave feedback, visit the CSP Roadmap proposal.
#13926 953a249 Thanks @ematipico! - Adds a new Astro Adapter Feature called experimentalStaticHeaders to allow your adapter to receive the Headers for rendered static pages.

Adapters that enable support for this feature can access header values directly, affecting their handling of some Astro features such as Content Security Policy (CSP). For example, Astro will no longer serve the CSP <meta http-equiv="content-security-policy"> element in static pages to adapters with this support.

Astro will serve the value of the header inside a map that can be retrieved from the hook astro:build:generated. Adapters can read this mapping and use their hosting headers capabilities to create a configuration file.

A new field called experimentalRouteToHeaders will contain a map of Map<IntegrationResolvedRoute, Headers> where the Headers type contains the headers emitted by the rendered static route.

To enable support for this experimental Astro Adapter Feature, add it to your adapterFeatures in your adapter config:
```
// my-adapter.mjs
export default function createIntegration() {
  return {
    name: '@example/my-adapter',
    hooks: {
      'astro:config:done': ({ setAdapter }) => {
        setAdapter({
          name: '@example/my-adapter',
          serverEntrypoint: '@example/my-adapter/server.js',
          adapterFeatures: {
            experimentalStaticHeaders: true,
          },
        });
      },
    },
  };
}
```
See the Adapter API docs for more information about providing adapter features.
#13697 af83b85 Thanks @benosmac! - Fixes issues with fallback route pattern matching when i18n.routing.fallbackType is rewrite.
- Adds conditions for route matching in generatePath when building fallback routes and checking for existing translated pages
Now for a route to be matched it needs to be inside a named [locale] folder. This fixes an issue where route.pattern.test() incorrectly matched dynamic routes, causing the page to be skipped.
- Adds conditions for route matching in findRouteToRewrite
Now the requested pathname must exist in route.distURL for a dynamic route to match. This fixes an issue where route.pattern.test() incorrectly matched dynamic routes, causing the build to fail.
#13924 1cd8c3b Thanks @qw-in! - Fixes an edge case where isPrerendered was incorrectly set to false for static redirects.
#13926 953a249 Thanks @ematipico! - Fixes an issue where the experimental CSP meta element wasn't placed in the <head> element as early as possible, causing these policies to not apply to styles and scripts that came before the meta element.

astro

withastro/astro

v5.9.2 Jun 9

Patch Changes

#13919 423fe60 Thanks @ematipico! - Fixes a bug where Astro added quotes to the CSP resources.

Only certain resources require quotes (e.g. 'self' but not https://cdn.example.com), so Astro no longer adds quotes to any resources. You must now provide the quotes yourself for resources such as 'self' when necessary:
```
export default defineConfig({
  experimental: {
    csp: {
      styleDirective: {
        resources: [
-          "self",
+          "'self'",
          "https://cdn.example.com"
        ]
      }
    }
  }
})
```
#13914 76c5480 Thanks @ematipico! - BREAKING CHANGE to the experimental Content Security Policy feature only

Removes support for experimental Content Security Policy (CSP) when using the <ClientRouter /> component for view transitions.

It is no longer possible to enable experimental CSP while using Astro's view transitions. Support was already unstable with the <ClientRouter /> because CSP required making its underlying implementation asynchronous. This caused breaking changes for several users and therefore, this PR removes support completely.

If you are currently using the component for view transitions, please remove the experimental CSP flag as they cannot be used together.
```
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
-   csp: true
   }
});
```
Alternatively, to continue using experimental CSP in your project, you can consider migrating to the browser native View Transition API and remove the <ClientRouter /> from your project. You may be able to achieve similar results if you are not using Astro's enhancements to the native View Transitions and Navigation APIs.

Support might be reintroduced in future releases. You can follow this experimental feature's development in the CSP RFC.

astro

withastro/astro

v5.9.1 Jun 7

Patch Changes

#13899 7a1303d Thanks @reknih! - Fix bug where error pages would return invalid bodies if the upstream response was compressed
#13902 051bc30 Thanks @arHSM! - Fixes a bug where vite virtual module ids were incorrectly added in the dev server
#13905 81f71ca Thanks @jsparkdev! - Fixes wrong contents in CSP meta tag.
#13907 8246bcc Thanks @martrapp! - Fixes a bug that caused view transition names to be lost.
#13901 37fa0a2 Thanks @ansg191! - fix fallback not being removed when server island is rendered

astro

withastro/astro

v5.9.0 Jun 5

Minor Changes

#13802 0eafe14 Thanks @ematipico! - Adds experimental Content Security Policy (CSP) support

CSP is an important feature to provide fine-grained control over resources that can or cannot be downloaded and executed by a document. In particular, it can help protect against cross-site scripting (XSS) attacks.

Enabling this feature adds additional security to Astro's handling of processed and bundled scripts and styles by default, and allows you to further configure these, and additional, content types. This new experimental feature has been designed to work in every Astro rendering environment (static pages, dynamic pages and single page applications), while giving you maximum flexibility and with type-safety in mind.

It is compatible with most of Astro's features such as client islands, and server islands, although Astro's view transitions using the <ClientRouter /> are not yet fully supported. Inline scripts are not supported out of the box, but you can provide your own hashes for external and inline scripts.

To enable this feature, add the experimental flag in your Astro config:
```
// astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    csp: true,
  },
});
```
For more information on enabling and using this feature in your project, see the Experimental CSP docs.

For a complete overview, and to give feedback on this experimental API, see the Content Security Policy RFC.

#13850 1766d22 Thanks @ascorbic! - Provides a Markdown renderer to content loaders

When creating a content loader, you will now have access to a renderMarkdown function that allows you to render Markdown content directly within your loaders. It uses the same settings and plugins as the renderer used for Markdown files in Astro, and follows any Markdown settings you have configured in your Astro project.

This allows you to render Markdown content from various sources, such as a CMS or other data sources, directly in your loaders without needing to preprocess the Markdown content separately.

import type { Loader } from 'astro/loaders';
import { loadFromCMS } from './cms';

export function myLoader(settings): Loader {
  return {
    name: 'my-loader',
    async load({ renderMarkdown, store }) {
      const entries = await loadFromCMS();

      store.clear();

      for (const entry of entries) {
        // Assume each entry has a 'content' field with markdown content
        store.set(entry.id, {
          id: entry.id,
          data: entry,
          rendered: await renderMarkdown(entry.content),
        });
      }
    },
  };
}

The return value of renderMarkdown is an object with two properties: html and metadata. These match the rendered property of content entries in content collections, so you can use them to render the content in your components or pages.

---
import { getEntry, render } from 'astro:content';
const entry = await getEntry('my-collection', Astro.params.id);
const { Content } = await render(entry);
---

<Content />

For more information, see the Content Loader API docs.

#13887 62f0668 Thanks @yanthomasdev! - Adds an option for integration authors to suppress adapter warning/errors in supportedAstroFeatures. This is useful when either an warning/error isn't applicable in a specific context or the default one might conflict and confuse users.

To do so, you can add suppress: "all" (to suppress both the default and custom message) or suppress: "default" (to only suppress the default one):
```
setAdapter({
  name: 'my-astro-integration',
  supportedAstroFeatures: {
    staticOutput: 'stable',
    hybridOutput: 'stable',
    sharpImageService: {
      support: 'limited',
      message:
        "The sharp image service isn't available in the deploy environment, but will be used by prerendered pages on build.",
      suppress: 'default',
    },
  },
});
```
For more information, see the Adapter API reference docs.

@astrojs/cloudflare

withastro/astro

v2.5.4 Jun 5

Patch Changes

#13817 b7258f1 Thanks @yanthomasdev! - Clarifies and reduces a few logs when starting the dev server with @astrojs/cloudflare.

Warnings about sharp support will now be suppressed when you have explicitly set an imageService option.
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

@astrojs/vercel

withastro/astro

v8.1.5 Jun 4

Patch Changes

#13679 4a8f193 Thanks @moonclavedev! - Handle SVG images correctly in build image service

@astrojs/sitemap

withastro/astro

v3.4.1 Jun 4

Patch Changes

#13871 8a1e849 Thanks @blimmer! - Uncaught errors in the filter method will now bubble, causing the astro build to fail.

@astrojs/rss

withastro/astro

v4.0.12 Jun 4

Patch Changes

#13867 c947c28 Thanks @Adriel-M! - Fixes a missing type attribute when providing a XSLT stylesheet

create-astro

withastro/astro

v4.12.1 May 29

Patch Changes

#12529 485c2f0 Thanks @apatel369! - Fixes an issue where installing Astro beta using create-astro displays the wrong Astro version in the installation messages.

@astrojs/web-vitals

withastro/astro

v4.0.0 May 29

Patch Changes

Updated dependencies [03435f8]:
- @astrojs/db@0.15.0

@astrojs/db

withastro/astro

v0.15.0 May 29

Minor Changes

#13815 03435f8 Thanks @jonaspm! - Upgraded drizzle-orm to latest v0.42.0

@astrojs/telemetry

withastro/astro

v3.3.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

@astrojs/mdx

withastro/astro

v4.3.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.2

@astrojs/upgrade

withastro/astro

v0.6.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

@astrojs/preact

withastro/astro

v4.1.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

@astrojs/markdown-remark

withastro/astro

v6.3.2 May 22

Patch Changes

Updated dependencies [3c3b492]:
- @astrojs/prism@3.3.0

@astrojs/react

withastro/astro

v4.3.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

@astrojs/solid-js

withastro/astro

v5.1.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

create-astro

withastro/astro

v4.12.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

@astrojs/vue

withastro/astro

v5.1.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

@astrojs/markdoc

withastro/astro

v0.15.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

Patch Changes

Updated dependencies [3c3b492]:
- @astrojs/prism@3.3.0
- @astrojs/markdown-remark@6.3.2

@astrojs/svelte

withastro/astro

v7.1.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

@astrojs/prism

withastro/astro

v3.3.0 May 22

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

@astrojs/netlify

withastro/astro

v6.3.4 May 21

Patch Changes

#13799 7036b05 Thanks @Lofty-Brambles! - Fixes an issue where the adapter didn't take into consideration the outDir configuration.
#13830 9371a67 Thanks @Lofty-Brambles! - Fixes an issue with SVGs not rendering with image-cdn enabled, due to invalid source path parsing.
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

@astrojs/node

withastro/astro

v9.2.2 May 21

Patch Changes

#13507 660e83f Thanks @TheOtterlord! - Handle errors where a module is not found when loading the server entrypoint

astro-antfustyle-theme

lin-stephanie/astro-antfustyle-theme

v2.1.0 May 20

🚀 Features

Integrate Giscus comments - by @lin-stephanie in #28 (fb951)
Add UI.postMetaStyle to set post metadata style ('minimal' for plain text, 'icon' for icon-prefixed); hide modified date on mobile - by @lin-stephanie (29e8a)

🐞 Bug Fixes

Missing shadow on mobile toc panel & docs error - by @lin-stephanie (1368d)
Icon jitter when toggling code collapse - by @lin-stephanie (0ffec)

💅 Refactors

Load medium-zoom only on post pages & format code - by @lin-stephanie (ae6d6)

🏡 Chore

Update docs for Giscus and UI.postMetaStyle - by @lin-stephanie (96cd0)
Update deps - by @lin-stephanie (14c02)

View changes on GitHub

@astrojs/netlify

withastro/astro

v6.3.3 May 13

Patch Changes

#13792 7910fea Thanks @alexeyzimarev! - Unify imported images detection across adapters
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

@astrojs/cloudflare

withastro/astro

v2.5.3 May 13

Patch Changes

#13792 7910fea Thanks @alexeyzimarev! - Unify imported images detection across adapters
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

@astrojs/db

withastro/astro

v0.14.14 May 12

Patch Changes

#13772 83193d4 Thanks @Adammatthiesen! - Fix options parsing for the libsql client connection to ensure that proper values are being set when adding URLSearchParams to the ASTRO_DB_REMOTE_URL
#13783 1609044 Thanks @Adammatthiesen! - Modify Database type to allow transactions to be properly typed now that Astro Studio has sunset.

@astrojs/sitemap

withastro/astro

v3.4.0 May 12

Minor Changes

#13753 90293de Thanks @mattyoho! - Customize the filenames of sitemap XML files generated by the @astro/sitemap integration by setting filenameBase in the integration configuration settings. This may be useful when deploying an Astro site at a path on a domain with preexisting sitemap files.

Generated sitemap files will appear at /sitemap-0.xml and /sitemap-index.xml by default, which may conflict with preexisting files. Set filenameBase to a custom value to avoid that if so:
```
import { defineConfig } from 'astro/config';
import sitemap from '@astrojs/sitemap';

export default defineConfig({
  site: 'https://example.com',
  integrations: [
    sitemap({
      filenameBase: 'astronomy-sitemap',
    }),
  ],
});
```
This will yield sitemap and index files as https://example.com/astronomy-sitemap-0.xml and https://example.com/astronomy-sitemap-index.xml.

@astrojs/starlight

withastro/starlight

v0.34.3 May 8

Patch Changes

#3058 274cc06 Thanks @techfg! - Fixes display of focus indicator around site title
#3181 449c822 Thanks @HiDeoo! - Fixes an issue where all headings in Markdown and MDX content were rendered with a clickable anchor link, even in non-Starlight pages.
#3168 ca693fe Thanks @jsparkdev! - Updates Korean langage support with improvements and missing translations

@astrojs/starlight

withastro/starlight

v0.34.2 May 1

Patch Changes

#3153 ea31f46 Thanks @SuperKXT! - Fixes hover styles for highlighted directory in FileTree component.
#2905 b5232bc Thanks @HiDeoo! - Fixes a potential issue for projects with dynamic routes added by an user, an Astro integration, or a Starlight plugin where some styles could end up being missing.
#3165 80a7871 Thanks @KianNH! - Increases maxBuffer for an internal spawnSync() call to support larger Git commit histories when using Starlight's lastUpdated feature.
#3158 d1f3c8b Thanks @heisenberg0924! - Adds Hungarian language support

astro-antfustyle-theme

lin-stephanie/astro-antfustyle-theme

v2.0.0 Apr 30

🚨 Breaking Changes

Upgrade from Astro 4.16 to Astro 5.7 and more - by @lin-stephanie in #25 (089b9)

🏡 Chore

Update docs for Astro 5.7 upgrade - by @lin-stephanie (ef781)

View changes on GitHub

@astrojs/vue

withastro/astro

v5.0.13 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/studio

withastro/astro

v0.1.9 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/svelte

withastro/astro

v7.0.13 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/netlify

withastro/astro

v6.3.2 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

@astrojs/solid-js

withastro/astro

v5.0.10 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/react

withastro/astro

v4.2.7 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/preact

withastro/astro

v4.0.11 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/mdx

withastro/astro

v4.2.6 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/cloudflare

withastro/astro

v2.5.2 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

@astrojs/db

withastro/astro

v0.14.13 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE
Updated dependencies [c3e80c2]:
- @astrojs/studio@0.1.9

@astrojs/markdoc

withastro/astro

v0.14.2 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/alpinejs

withastro/astro

v0.4.8 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/vue

withastro/astro

v5.0.12 Apr 29

Patch Changes

#13720 e1cd1ae Thanks @florian-lefebvre! - Fixes SSR renderer type

@astrojs/svelte

withastro/astro

v7.0.12 Apr 29

Patch Changes

#13720 e1cd1ae Thanks @florian-lefebvre! - Fixes SSR renderer type

@astrojs/react

withastro/astro

v4.2.6 Apr 29

Patch Changes

#13720 e1cd1ae Thanks @florian-lefebvre! - Fixes SSR renderer type

create-astro

withastro/astro

v4.11.4 Apr 28

Patch Changes

#13703 659904b Thanks @ascorbic! - Fixes an issue when installing dependencies with pnpm.

astro-loader-bluesky-posts

lin-stephanie/astro-loaders

v1.2.2 Apr 27

Patch Changes (`aec3423`)

Update the entry Zod schema
Resolve <Content /> becomes non-functional when fetchThread: true is set

@astrojs/starlight

withastro/starlight

v0.34.1 Apr 24

Patch Changes

#3140 f6eb1d5 Thanks @HiDeoo! - Fixes a text selection issue for heading with a clickable anchor link when using double or triple click to select text.
#3148 dc8b6d5 Thanks @HiDeoo! - Fixes a regression of the Starlight icon color when using the credits configuration option.

@astrojs/upgrade

withastro/astro

v0.5.2 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/underscore-redirects

withastro/astro

v0.6.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/telemetry

withastro/astro

v3.2.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/vercel

withastro/astro

v8.1.4 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/studio

withastro/astro

v0.1.8 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/web-vitals

withastro/astro

v3.0.2 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/vue

withastro/astro

v5.0.11 Apr 23

Patch Changes

#13663 a19a185 Thanks @florian-lefebvre! - Improves type-safety of renderers

@astrojs/svelte

withastro/astro

v7.0.11 Apr 23

Patch Changes

#13663 a19a185 Thanks @florian-lefebvre! - Improves type-safety of renderers

@astrojs/solid-js

withastro/astro

v5.0.9 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/sitemap

withastro/astro

v3.3.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/node

withastro/astro

v9.2.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/react

withastro/astro

v4.2.5 Apr 23

Patch Changes

#13663 a19a185 Thanks @florian-lefebvre! - Improves type-safety of renderers

@astrojs/netlify

withastro/astro

v6.3.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code
Updated dependencies [5dd2d3f]:
- @astrojs/underscore-redirects@0.6.1

@astrojs/preact

withastro/astro

v4.0.10 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

create-astro

withastro/astro

v4.11.3 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/cloudflare

withastro/astro

v2.5.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code
Updated dependencies [5dd2d3f]:
- @astrojs/underscore-redirects@0.6.1

@astrojs/mdx

withastro/astro

v4.2.5 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/markdoc

withastro/astro

v0.14.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/alpinejs

withastro/astro

v0.4.7 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/db

withastro/astro

v0.14.12 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code
Updated dependencies [5dd2d3f]:
- @astrojs/studio@0.1.8

@astrojs/starlight-tailwind

withastro/starlight

v4.0.1 Apr 17

Patch Changes

#3132 5959919 Thanks @HiDeoo! - Fixes an issue where all border styles were not reset by the Starlight’s Tailwind compatibility package like in Tailwind base styles.

create-astro

withastro/astro

v4.11.2 Apr 17

Patch Changes

#13636 a9fd03f Thanks @sarah11918! - Updates the wording for choosing the "minimal" starter template options

@astrojs/starlight-tailwind

withastro/starlight

v4.0.0 Apr 16

Major Changes

#2322 f14eb0c Thanks @HiDeoo! - ⚠️ BREAKING CHANGE: The minimum supported version of Starlight is now 0.34.0

Please use the @astrojs/upgrade command to upgrade your project:
```
npx @astrojs/upgrade
```

#2322 f14eb0c Thanks @HiDeoo! - Adds support for Tailwind v4, drops support for Tailwind v3.

⚠️ BREAKING CHANGE: Tailwind v3 is no longer supported. Tailwind v4 support in Astro is now provided using a Vite plugin and the Astro Tailwind integration is no longer required.

Remove the Astro Tailwind integration. The Astro Tailwind integration is no longer required with Tailwind v4.

 // astro.config.mjs
 import { defineConfig } from "astro/config";
 import starlight from "@astrojs/starlight";
-import tailwind from "@astrojs/tailwind";

 export default defineConfig({
   integrations: [
     starlight({
       title: "Docs with Tailwind",
       customCss: ["./src/tailwind.css"],
     }),
-    tailwind({ applyBaseStyles: false }),
   ],
 });

Install Tailwind v4. Install the latest version of the tailwindcss and @tailwindcss/vite packages.

Use the astro add tailwind command to install and configure both packages:
```
npx astro add tailwind
```

Update Tailwind base styles. Tailwind CSS base styles needs to be updated for Tailwind v4 and also to use Starlight Tailwind CSS.

/* src/tailwind.css */
-@tailwind base;
-@tailwind components;
-@tailwind utilities;
+@layer base, starlight, theme, components, utilities;
+
+@import '@astrojs/starlight-tailwind';
+@import 'tailwindcss/theme.css' layer(theme);
+@import 'tailwindcss/utilities.css' layer(utilities);
+
+@theme {
+	/*
+	Configure your Tailwind theme that will be used by Starlight.
+	https://starlight.astro.build/guides/css-and-tailwind/#styling-starlight-with-tailwind
+	*/
+}
+
+/*
+Add additional Tailwind styles to this file:
+https://tailwindcss.com/docs/adding-custom-styles#using-custom-css
+*/

Update Tailwind customizations. If you previously customized your Tailwind theme configuration in the tailwind.config.mjs file, such customizations are now defined through CSS using the @theme block in your Tailwind base styles.

Locate existing customizations in your tailwind.config.mjs file. The following example defines customizations for the accent colors, gray scale, and font families used by Starlight:

// tailwind.config.mjs
import starlightPlugin from '@astrojs/starlight-tailwind';
import colors from 'tailwindcss/colors';

/** @type {import('tailwindcss').Config} */
export default {
  content: ['./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}'],
  theme: {
    extend: {
      colors: {
        // Custom accent colors.
        accent: colors.fuchsia,
        // Custom gray scale.
        gray: colors.slate,
      },
      fontFamily: {
        // Custom text font.
        sans: ['"Atkinson Hyperlegible"'],
        // Custom code font.
        mono: ['"IBM Plex Mono"'],
      },
    },
  },
  plugins: [starlightPlugin()],
};

The above customizations can be migrated to the new @theme block in the file containing your Tailwind base styles as follows:

/* src/tailwind.css */
@layer base, starlight, theme, components, utilities;

@import '@astrojs/starlight-tailwind';
@import 'tailwindcss/theme.css' layer(theme);
@import 'tailwindcss/utilities.css' layer(utilities);

@theme {
  /* Custom accent colors. */
  --color-accent-50: var(--color-fuchsia-50);
  --color-accent-100: var(--color-fuchsia-100);
  --color-accent-200: var(--color-fuchsia-200);
  --color-accent-300: var(--color-fuchsia-300);
  --color-accent-400: var(--color-fuchsia-400);
  --color-accent-500: var(--color-fuchsia-500);
  --color-accent-600: var(--color-fuchsia-600);
  --color-accent-700: var(--color-fuchsia-700);
  --color-accent-800: var(--color-fuchsia-800);
  --color-accent-900: var(--color-fuchsia-900);
  --color-accent-950: var(--color-fuchsia-950);
  /* Custom gray scale. */
  --color-gray-50: var(--color-slate-50);
  --color-gray-100: var(--color-slate-100);
  --color-gray-200: var(--color-slate-200);
  --color-gray-300: var(--color-slate-300);
  --color-gray-400: var(--color-slate-400);
  --color-gray-500: var(--color-slate-500);
  --color-gray-600: var(--color-slate-600);
  --color-gray-700: var(--color-slate-700);
  --color-gray-800: var(--color-slate-800);
  --color-gray-900: var(--color-slate-900);
  --color-gray-950: var(--color-slate-950);
  /* Custom text font. */
  --font-sans: 'Atkinson Hyperlegible';
  /* Custom code font. */
  --font-mono: 'IBM Plex Mono';
}

We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.

For full details about upgrading from Tailwind v3 to v4, see the official upgrade guide.

@astrojs/starlight

withastro/starlight

v0.34.0 Apr 16

Minor Changes

#2322 f14eb0c Thanks @HiDeoo! - Groups all of Starlight's CSS declarations into a single starlight cascade layer.

This change allows for easier customization of Starlight's CSS as any custom unlayered CSS will override the default styles. If you are using cascade layers in your custom CSS, you can use the @layer CSS at-rule to define the order of precedence for different layers including the ones used by Starlight.

We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.
#3122 3a087d8 Thanks @delucis! - Removes default attrs and content values from head entries parsed using Starlight’s schema.

Previously when adding head metadata via frontmatter or user config, Starlight would automatically add values for attrs and content if not provided. Now, these properties are left undefined.

This makes it simpler to add tags in route middleware for example as you no longer need to provide empty values for attrs and content:
```
head.push({
  tag: 'style',
  content: 'div { color: red }'
- attrs: {},
});
head.push({
  tag: 'link',
- content: ''
  attrs: { rel: 'me', href: 'https://example.com' },
});
```
This is mostly an internal API but if you are overriding Starlight’s Head component or processing head entries in some way, you may wish to double check your handling of Astro.locals.starlightRoute.head is compatible with attrs and content potentially being undefined.
#3033 8c19678 Thanks @delucis! - Adds support for generating clickable anchor links for headings.

By default, Starlight now renders an anchor link beside headings in Markdown and MDX content. A new <AnchorHeading> component is available to achieve the same thing in custom pages built using <StarlightPage>.

If you want to disable this new Markdown processing set the markdown.headingLinks option in your Starlight config to false:
```
starlight({
  title: 'My docs',
  markdown: {
    headingLinks: false,
  },
}),
```
⚠️ BREAKING CHANGE: The minimum supported version of Astro is now v5.5.0.

Please update Starlight and Astro together:
```
npx @astrojs/upgrade
```

#2322 f14eb0c Thanks @HiDeoo! - Removes Shiki css-variables theme fallback.

⚠️ BREAKING CHANGE:

Previously, Starlight used to automatically provide a fallback theme for Shiki, the default syntax highlighter built into Astro if the configured Shiki theme was not github-dark.

This fallback was only relevant when the default Starlight code block renderer, Expressive Code, was disabled and Shiki was used. Starlight no longer provides this fallback.

If you were relying on this behavior, you now manually need to update your Astro configuration to use the Shiki css-variables theme to match the previous behavior.

import { defineConfig } from 'astro/config';

export default defineConfig({
+ markdown: {
+   shikiConfig: {
+     theme: 'css-variables',
+   },
+ },
});

Additionally, you can use custom CSS to control the appearance of the code blocks. Here are the previously used CSS variables for the fallback theme:

:root {
  --astro-code-foreground: var(--sl-color-white);
  --astro-code-background: var(--sl-color-gray-6);
  --astro-code-token-constant: var(--sl-color-blue-high);
  --astro-code-token-string: var(--sl-color-green-high);
  --astro-code-token-comment: var(--sl-color-gray-2);
  --astro-code-token-keyword: var(--sl-color-purple-high);
  --astro-code-token-parameter: var(--sl-color-red-high);
  --astro-code-token-function: var(--sl-color-red-high);
  --astro-code-token-string-expression: var(--sl-color-green-high);
  --astro-code-token-punctuation: var(--sl-color-gray-2);
  --astro-code-token-link: var(--sl-color-blue-high);
}

Patch Changes

#3118 77a1104 Thanks @delucis! - Fixes passing imported SVGs to the frontmatter prop of the <StarlightPage> component in Astro ≥5.7.0

@astrojs/starlight-markdoc

withastro/starlight

v0.4.0 Apr 16

Minor Changes

#3033 8c19678 Thanks @delucis! - Adds support for generating clickable anchor links for headings.

By default, the Starlight Markdoc preset now includes a default heading node, which renders an anchor link beside headings in your Markdoc content.

If you want to disable this new feature, pass headingLinks: false in your Markdoc config:
```
export default defineMarkdocConfig({
  // Disable the default heading anchor link support
  extends: [starlightMarkdoc({ headingLinks: false })],
});
```
⚠️ BREAKING CHANGE: The minimum supported peer version of Starlight is now v0.34.0.

Please update Starlight and the Starlight Markdoc preset together:
```
npx @astrojs/upgrade
```

@astrojs/node

withastro/astro

v9.2.0 Apr 15

Minor Changes

#13527 2fd6a6b Thanks @ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.

Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:
```
---
export const prerender = false; // Not needed with 'server' output
const cart = await Astro.session.get('cart');
---

<a href="/checkout">🛒 {cart?.length ?? 0} items</a>
```
Configuring session storage

Sessions require a storage driver to store the data. The Node, Cloudflare and Netlify adapters automatically configure a default driver for you, but other adapters currently require you to specify a custom storage driver in your configuration.

If you are using an adapter that doesn't have a default driver, or if you want to choose a different driver, you can configure it using the session configuration option:
```
import { defineConfig } from 'astro/config';
import vercel from '@astrojs/vercel';

export default defineConfig({
  adapter: vercel(),
  session: {
    driver: 'upstash',
  },
});
```
Using sessions

Sessions are available in on-demand rendered pages, API endpoints, actions and middleware.

In pages and components, you can access the session using Astro.session:
```
---
const cart = await Astro.session.get('cart');
---

<a href="/checkout">🛒 {cart?.length ?? 0} items</a>
```
In endpoints, actions, and middleware, you can access the session using context.session:
```
export async function GET(context) {
  const cart = await context.session.get('cart');
  return Response.json({ cart });
}
```
If you attempt to access the session when there is no storage driver configured, or in a prerendered page, the session object will be undefined and an error will be logged in the console:
```
---
export const prerender = true;
const cart = await Astro.session?.get('cart'); // Logs an error. Astro.session is undefined
---
```
Upgrading from Experimental to Stable

If you were previously using the experimental API, please remove the experimental.session flag from your configuration:
```
import { defineConfig } from 'astro/config';
import node from '@astrojs/node';

export default defineConfig({
   adapter: node({
     mode: "standalone",
   }),
-  experimental: {
-    session: true,
-  },
});
```
See the sessions guide for more information.

@astrojs/markdoc

withastro/astro

v0.14.0 Apr 15

Minor Changes

#13578 406501a Thanks @stramel! - The SVG import feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.

This feature allows you to import SVG files directly into your Astro project as components and inline them into your HTML.

To use this feature, import an SVG file in your Astro project, passing any common SVG attributes to the imported component.
```
---
import Logo from './path/to/svg/file.svg';
---

<Logo <Logo width={64} height={64} fill="currentColor" />
```
If you have been waiting for stabilization before using the SVG Components feature, you can now do so.

If you were previously using this feature, please remove the experimental flag from your Astro config:
```
import { defineConfig } from 'astro'

export default defineConfig({
-  experimental: {
-    svg: true,
-  }
})
```
Additionally, a few features that were available during the experimental stage were removed in a previous release. Please see the v5.6.0 changelog for details if you have not yet already updated your project code for the experimental feature accordingly.

Please see the SVG Components guide in docs for more about this feature.

@astrojs/starlight-markdoc

withastro/starlight

v0.3.1 Apr 14

Patch Changes

#3090 fc3ffa8 Thanks @delucis! - Adds support for newer versions of @astrojs/markdoc
#3109 b5cc1b4 Thanks @dhruvkb! - Updates Expressive Code to v0.41.1