[deps]: Update bun minor

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/check (source)	0.9.4 -> 0.9.6
@astrojs/mdx (source)	4.0.3 -> 4.3.12
@astrojs/tailwind (source)	5.1.4 -> 5.1.5
@fontsource/dm-sans (source)	5.1.0 -> 5.2.8
astro (source)	5.15.9 -> 5.16.3
marked (source)	15.0.4 -> 15.0.12
tailwindcss (source)	3.4.17 -> 3.4.18
typescript (source)	5.7.2 -> 5.9.3

---

Release Notes

withastro/astro (@​astrojs/check)

v0.9.6

Patch Changes

• #​14740 abfed97 Thanks @​ArmandPhilippot! - Fixes link targets in documentation following repository relocation.

• Updated dependencies [abfed97]:

  • @​astrojs/language-server@​2.16.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.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 [6bd5f75]:
  • @​astrojs/markdown-remark@​6.3.3

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

v4.0.8

Compare Source

Patch Changes

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

v4.0.7

Compare Source

Patch Changes

• #​13011 cf30880 Thanks @​ascorbic! - Upgrades Vite

v4.0.6

Compare Source

Patch Changes

• Updated dependencies [3d89e62]:
  • @​astrojs/markdown-remark@​6.0.2

v4.0.5

Compare Source

Patch Changes

• #​12959 3a267f3 Thanks @​bluwy! - Reverts 9a3b48c which caused a regression for rendering inline MDX components and MDX files from content collections

v4.0.4

Compare Source

Patch Changes

• #​12921 aeb7e1a Thanks @​ascorbic! - Fixes a bug that caused Image component to be imported on MDX pages that did not include images

• #​12913 9a3b48c Thanks @​bluwy! - Makes internal check() function a no-op to allow faster component renders and prevent React 19 component warnings

withastro/astro (@​astrojs/tailwind)

v5.1.5

Compare Source

Patch Changes

• #​13011 cf30880 Thanks @​ascorbic! - Upgrades Vite

fontsource/font-files (@​fontsource/dm-sans)

v5.2.8

Compare Source

v5.2.7

Compare Source

v5.2.6

Compare Source

v5.2.5

Compare Source

v5.2.4

Compare Source

v5.2.1

Compare Source

v5.2.0

Compare Source

v5.1.1

Compare Source

withastro/astro (astro)

v5.16.3

Compare Source

Patch Changes

• #​14889 4bceeb0 Thanks @​florian-lefebvre! - Fixes actions types when using specific TypeScript configurations

• #​14929 e0f277d Thanks @​matthewp! - Fixes authentication bypass via double URL encoding in middleware

  Prevents attackers from bypassing path-based authentication checks using multi-level URL encoding (e.g., /%2561dmin instead of /%61dmin). Pathnames are now validated after decoding to ensure no additional encoding remains.

v5.16.2

Compare Source

Patch Changes

• #​14876 b43dc7f Thanks @​florian-lefebvre! - Fixes a vite warning log during builds when using npm

• #​14884 10273e0 Thanks @​florian-lefebvre! - Fixes a case where setting the status of a page to 404 in ssr would show an empty page (or 404.astro page if provided) instead of using the current page

v5.16.1

Compare Source

Patch Changes

• #​14769 b43ee71 Thanks @​adriandlam! - Fixes an unhandled rejection issue when using Astro with Vercel Workflow DevKit

• #​14761 345eb22 Thanks @​ooga! - Updates button attributes types to allow command and commandfor

• #​14866 65e214b Thanks @​GameRoMan! - Fixes Astro.glob to be correctly marked as deprecated

• #​14894 1ad9a5b Thanks @​delucis! - Fixes support for Astro component rendering in Vitest test suites using a “client” environment such as happy-dom or jsdom

• #​14782 abed929 Thanks @​florian-lefebvre! - Improves syncing

v5.16.0

Compare Source

Minor Changes

• #​13880 1a2ed01 Thanks @​azat-io! - Adds experimental SVGO optimization support for SVG assets

  Astro now supports automatic SVG optimization using SVGO during build time. This experimental feature helps reduce SVG file sizes while maintaining visual quality, improving your site's performance.

  To enable SVG optimization with default settings, add the following to your astro.config.mjs:

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

  To customize optimization, pass a SVGO configuration object:

  export default defineConfig({
    experimental: {
      svgo: {
        plugins: [
          'preset-default',
          {
            name: 'removeViewBox',
            active: false,
          },
        ],
      },
    },
  });

  For more information on enabling and using this feature in your project, see the experimental SVG optimization docs.

• #​14810 2e845fe Thanks @​ascorbic! - Adds a hint for code agents to use the --yes flag to skip prompts when running astro add

• #​14698 f42ff9b Thanks @​mauriciabad! - Adds the ActionInputSchema utility type to automatically infer the TypeScript type of an action's input based on its Zod schema

  For example, this type can be used to retrieve the input type of a form action:

  import { type ActionInputSchema, defineAction } from 'astro:actions';
  import { z } from 'astro/zod';
  
  const action = defineAction({
    accept: 'form',
    input: z.object({ name: z.string() }),
    handler: ({ name }) => ({ message: `Welcome, ${name}!` }),
  });
  
  type Schema = ActionInputSchema<typeof action>;
  // typeof z.object({ name: z.string() })
  
  type Input = z.input<Schema>;
  // { name: string }

• #​14574 4356485 Thanks @​jacobdalamb! - Adds new CLI shortcuts available when running astro preview:

  • o + enter: open the site in your browser
  • q + enter: quit the preview
  • h + enter: print all available shortcuts

Patch Changes

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

• #​14609 d774306 Thanks @​florian-lefebvre! - Improves astro info

• #​14796 c29a785 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Updates the default subsets to ["latin"]

  Subsets have been a common source of confusion: they caused a lot of files to be downloaded by default. You now have to manually pick extra subsets.

  Review your Astro config and update subsets if you need, for example if you need greek characters:

  import { defineConfig, fontProviders } from "astro/config"
  
  export default defineConfig({
      experimental: {
          fonts: [{
              name: "Roboto",
              cssVariable: "--font-roboto",
              provider: fontProviders.google(),
  +            subsets: ["latin", "greek"]
          }]
      }
  })

markedjs/marked (marked)

v15.0.12

Compare Source

Bug Fixes

• use esbuild for accurate sourcemaps (#​3670) (7a6b2d7)

v15.0.11

Compare Source

Bug Fixes

• fix image alt text rendered to match common mark (#​3668) (2c0e47a)

v15.0.10

Compare Source

Bug Fixes

• fix non-breaking space in link url (#​3667) (e071e25)

v15.0.9

Compare Source

Bug Fixes

• fix link url with no closing parenthesis (#​3664) (72b6373)

v15.0.8

Compare Source

Bug Fixes

• fix emstrong inside escaped backticks (#​3652) (721dc58)

v15.0.7

Compare Source

Bug Fixes

• fix table rendered as heading (#​3612) (9ae87de)

v15.0.6

Compare Source

Bug Fixes

• fix strikethrough inside strong and em to follow gfm (#​3577) (7712a53)

v15.0.5

Compare Source

Bug Fixes

• allow strikethrough inside strong and em to follow gfm (#​3569) (8a01658)

tailwindlabs/tailwindcss (tailwindcss)

v3.4.18

Compare Source

Fixed

• Improve support for raw supports-[…] queries in arbitrary values (#​13605)
• Fix require.cache error when loaded through a TypeScript file in Node 22.18+ (#​18665)
• Support import.meta.resolve(…) in configs for new enough Node.js versions (#​18938)
• Allow using newer versions of postcss-load-config for better ESM and TypeScript PostCSS config support with the CLI (#​18938)
• Remove irrelevant utility rules when matching important classes (#​19030)

microsoft/TypeScript (typescript)

v5.9.3: TypeScript 5.9.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC).
• No specific changes for TypeScript 5.9.2 (Stable)
• fixed issues query for Typescript 5.9.3 (Stable).

Downloads are available on:

• npm

v5.9.2: TypeScript 5.9

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC).
• No specific changes for TypeScript 5.9.2 (Stable)

Downloads are available on:

• npm

v5.8.3: TypeScript 5.8.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).
• fixed issues query for Typescript 5.8.1 (RC).
• fixed issues query for Typescript 5.8.2 (Stable).
• fixed issues query for Typescript 5.8.3 (Stable).

Downloads are available on:

• npm

v5.8.2: TypeScript 5.8

Compare Source

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).
• fixed issues query for Typescript 5.8.1 (RC).
• fixed issues query for Typescript 5.8.2 (Stable).

Downloads are available on:

• npm

v5.7.3: TypeScript 5.7.3

Compare Source

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.7.0 (Beta).
• fixed issues query for Typescript 5.7.1 (RC).
• fixed issues query for Typescript 5.7.2 (Stable).
• fixed issues query for Typescript 5.7.3 (Stable).

Downloads are available on npm

---

Configuration

📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.