[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/check (source)	0.9.4 → 0.9.12
@astrojs/mdx (source)	4.0.8 → 4.3.14
@astrojs/react (source)	4.2.0 → 4.4.2
@astrojs/tailwind (source)	6.0.0 → 6.0.2

---

Release Notes

withastro/astro (@​astrojs/check)

v0.9.12

Compare Source

Patch Changes

• #​18455 7af66fc Thanks @​astro-factory! - Fixes the astro-check binary ignoring its first two command-line arguments, so flags such as --help, --root, --watch, and --tsconfig are respected again. If your scripts padded the arguments to work around this (for example, astro-check -- -- --tsconfig ./tsconfig.app.json), remove the padding.
• Updated dependencies [044148d]:
  • @​astrojs/language-server@2.17.3

v0.9.11

Compare Source

Patch Changes

• #​18445 d736df7 Thanks @​astro-factory! - Fixes the --preserveWatchOutput help text, which described the opposite of the flag's behavior. Setting it to true keeps output between checks in watch mode.

• #​18444 c55134c Thanks @​astro-factory! - Fixes astro check --watch exiting immediately when the project path contains node_modules or .git

v0.9.10

Compare Source

Patch Changes

• #​17447 b01a692 Thanks @​ocavue! - Update dependency yargs to version 18. See the yargs changelog for details.

v0.9.9

Compare Source

Patch Changes

• #​16471 f56bb3f Thanks @​delucis! - Adds support for TypeScript v6 to peer dependencies range

• Updated dependencies [8c62159]:

  • @​astrojs/language-server@2.16.7

v0.9.8

Compare Source

Patch Changes

• #​15892 a2f597d Thanks @​Princesseuh! - Fixes Astro not being able to find astro check sometimes

• Updated dependencies [7b4b254]:

  • @​astrojs/language-server@2.16.5

v0.9.7

Compare Source

Patch Changes

• #​15187 bbb5811 Thanks @​matthewp! - Update to Astro 6 beta

• #​15198 55107a1 Thanks @​HiDeoo! - Updates to Astro 6 beta

• Updated dependencies [bbb5811, df6d2d7]:

  • @​astrojs/language-server@2.16.1

v0.9.6

Patch Changes

• #​15187 bbb5811 Thanks @​matthewp! - Update to Astro 6 beta

• Updated dependencies [bbb5811]:

  • @​astrojs/language-server@2.16.1-beta.1

v0.9.5

Patch Changes

• d415d4e: When no errors or warnings are detected, display "0 errors" or "0 warnings" in a dimmed color on the console instead of red or yellow.

withastro/astro (@​astrojs/mdx)

v4.3.14

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@6.3.11

v4.3.13

Compare Source

Patch Changes

• Updated dependencies [d8305f8]:
  • @​astrojs/markdown-remark@6.3.10

v4.3.12

Compare Source

Patch Changes

• #​14813 e1dd377 Thanks @​ematipico! - Removes picocolors as dependency in favor of the fork piccolore.

v4.3.11

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@6.3.9

v4.3.10

Compare Source

Patch Changes

• #​14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

  The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

  See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

v4.3.9

Patch Changes

• #​14621 e3175d9 Thanks @​GameRoMan! - Updates vite version to fix CVE

v4.3.8

Patch Changes

• #​14591 3e887ec Thanks @​matthewp! - Adds TypeScript support for the components prop on MDX Content component when using await render(). Developers now get proper IntelliSense and type checking when passing custom components to override default MDX element rendering.

• #​14598 7b45c65 Thanks @​delucis! - Reduces terminal text styling dependency size by switching from kleur to picocolors

v4.3.7

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@6.3.8

v4.3.6

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@6.3.7

v4.3.5

Compare Source

Patch Changes

• #​14326 c24a8f4 Thanks @​jsparkdev! - Updates vite version to fix CVE

v4.3.4

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@6.3.6

v4.3.3

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@6.3.5

v4.3.2

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@6.3.4

v4.3.1

Compare Source

Patch Changes

• Updated dependencies [d8305f8]:
  • @​astrojs/markdown-remark@6.3.10

v4.3.0

Compare Source

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

v4.2.6

Compare Source

Patch Changes

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

v4.2.5

Compare Source

Patch Changes

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

v4.2.4

Compare Source

Patch Changes

• #​13596 3752519 Thanks @​jsparkdev! - update vite to latest version to fix CVE

• #​13547 360cb91 Thanks @​jsparkdev! - Updates vite to the latest version

v4.2.3

Compare Source

Patch Changes

• #​13526 ff9d69e Thanks @​jsparkdev! - update vite to the latest version

v4.2.2

Patch Changes

• #​13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

v4.2.1

Patch Changes

• #​13448 91c9503 Thanks @​ematipico! - Upgrade to shiki v3

• Updated dependencies [91c9503]:

  • @​astrojs/markdown-remark@6.3.1

v4.2.0

Compare Source

Minor Changes

• #​13352 cb886dc Thanks @​delucis! - Adds support for a new experimental.headingIdCompat flag

  By default, Astro removes a trailing - from the end of IDs it generates for headings ending with
  special characters. This differs from the behavior of common Markdown processors.

  You can now disable this behavior with a new configuration flag:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  
  export default defineConfig({
    experimental: {
      headingIdCompat: true,
    },
  });

  This can be useful when heading IDs and anchor links need to behave consistently across your site
  and other platforms such as GitHub and npm.

  If you are using the rehypeHeadingIds plugin directly, you can also pass this new option:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import { rehypeHeadingIds } from '@astrojs/markdown-remark';
  import { otherPluginThatReliesOnHeadingIDs } from 'some/plugin/source';
  
  export default defineConfig({
    markdown: {
      rehypePlugins: [
        [rehypeHeadingIds, { experimentalHeadingIdCompat: true }],
        otherPluginThatReliesOnHeadingIDs,
      ],
    },
  });

Patch Changes

• Updated dependencies [cb886dc, a3327ff]:
  • @​astrojs/markdown-remark@6.3.0

v4.1.1

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@6.2.1

v4.1.0

Compare Source

Minor Changes

• #​13254 1e11f5e Thanks @​p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown syntax in MDX files.

  Previously, Astro only allowed local images to be optimized when included using ![]() syntax. Astro's image service could only display remote images without any processing.

  Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.

  No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the JSX <img/> tag instead. Note that images located in your public/ folder are still never processed.

Patch Changes

• Updated dependencies [1e11f5e]:
  • @​astrojs/markdown-remark@6.2.0

withastro/astro (@​astrojs/react)

v4.4.2

Compare Source

Patch Changes

• #​14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

  The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

  See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

v4.4.1

Compare Source

Patch Changes

• #​14621 e3175d9 Thanks @​GameRoMan! - Updates vite version to fix CVE

v4.4.0

Compare Source

Minor Changes

• #​14386 f75f446 Thanks @​yanthomasdev! - Stabilizes the formerly experimental getActionState() and withState() functions introduced in @astrojs/react v3.4.0 used to integrate Astro Actions with React 19's useActionState() hook.

  This example calls a like action that accepts a postId and returns the number of likes. Pass this action to the withState() function to apply progressive enhancement info, and apply to useActionState() to track the result:

  import { actions } from 'astro:actions';
  import { withState } from '@astrojs/react/actions';
  import { useActionState } from 'react';
  
  export function Like({ postId }: { postId: string }) {
    const [state, action, pending] = useActionState(
      withState(actions.like),
      0, // initial likes
    );
  
    return (
      <form action={action}>
        <input type="hidden" name="postId" value={postId} />
        <button disabled={pending}>{state} ❤️</button>
      </form>
    );
  }
  

  You can also access the state stored by useActionState() from your action handler. Call getActionState() with the API context, and optionally apply a type to the result:

  import { defineAction } from 'astro:actions';
  import { z } from 'astro:schema';
  import { getActionState } from '@astrojs/react/actions';
  
  export const server = {
    like: defineAction({
      input: z.object({
        postId: z.string(),
      }),
      handler: async ({ postId }, ctx) => {
        const currentLikes = getActionState<number>(ctx);
        // write to database
        return currentLikes + 1;
      },
    }),
  };
  

  If you were previously using this experimental feature, you will need to update your code to use the new stable exports:

  // src/components/Form.jsx
  import { actions } from 'astro:actions';
  -import { experimental_withState } from '@astrojs/react/actions';
  +import { withState } from '@astrojs/react/actions';
  import { useActionState } from "react";

  // src/actions/index.ts
  import { defineAction, type SafeResult } from 'astro:actions';
  import { z } from 'astro:schema';
  -import { experimental_getActionState } from '@astrojs/react/actions';
  +import { getActionState } from '@astrojs/react/actions';

v4.3.1

Compare Source

Patch Changes

• #​14326 c24a8f4 Thanks @​jsparkdev! - Updates vite version to fix CVE

v4.3.0

Compare Source

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.

v4.2.7

Compare Source

Patch Changes

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

v4.2.6

Compare Source

Patch Changes

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

v4.2.5

Compare Source

Patch Changes

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

v4.2.4

Compare Source

Patch Changes

• #​13596 3752519 Thanks @​jsparkdev! - update vite to latest version to fix CVE

• #​13547 360cb91 Thanks @​jsparkdev! - Updates vite to the latest version

v4.2.3

Compare Source

Patch Changes

• #​13526 ff9d69e Thanks @​jsparkdev! - update vite to the latest version

v4.2.2

Compare Source

Patch Changes

• #​13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

v4.2.1

Compare Source

Patch Changes

• #​13323 80926fa Thanks @​ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

withastro/astro (@​astrojs/tailwind)

v6.0.2

Compare Source

Patch Changes

• #​13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

v6.0.1

Compare Source

Patch Changes

• #​13471 020c542 Thanks @​delucis! - Updates the README to indicate that the Tailwind integration is deprecated

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d0d089c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

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

Project	Deployment	Actions	Updated
code-snippets	Error		Oct 22, 2026 11:18am UTC