Update astro monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/mdx (source)	4.3.7 → 4.3.14
@astrojs/sitemap (source)	3.6.0 → 3.7.3
@astrojs/vue (source)	5.1.1 → 5.1.4

---

Release Notes

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

withastro/astro (@​astrojs/sitemap)

v3.7.3

Compare Source

Patch Changes

• #​16837 783c4a6 Thanks @​jdevalk! - Improves <lastmod> accuracy in the sitemap index. Each <sitemap> entry in sitemap-index.xml is now stamped with the most recent lastmod of the URLs in the child sitemap it points to, instead of repeating a single global date on every entry. When a child sitemap has no per-URL lastmod, the entry falls back to the lastmod option as before. This gives search engines a per-file freshness signal, so they can tell which child sitemaps actually changed without refetching all of them.

v3.7.2

Compare Source

Patch Changes

• #​15455 babf57f Thanks @​AhmadYasser1! - Fixes i18n fallback pages missing from the generated sitemap when using fallbackType: 'rewrite'.

v3.7.1

Compare Source

Patch Changes

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

• #​14956 0ff51df Thanks @​matthewp! - Updates usage of zod to own dependency rather than relying on astro/zod

• #​15036 f125a73 Thanks @​florian-lefebvre! - Updates how routes are retrieved to avoid relying on a deprecated API

• #​15373 14252b2 Thanks @​renovate! - Updates zod to v4

v3.7.0

Compare Source

Minor Changes

• #​14471 4296373 Thanks @​Slackluky! - Adds the ability to split sitemap generation into chunks based on customizable logic. This allows for better management of large sitemaps and improved performance. The new chunks option in the sitemap configuration allows users to define functions that categorize sitemap items into different chunks. Each chunk is then written to a separate sitemap file.

  integrations: [
    sitemap({
      serialize(item) { th
        return item
      },
      chunks: { // this property will be treated last on the configuration
        'blog': (item) => {  // will produce a sitemap file with `blog` name (sitemap-blog-0.xml)
          if (/blog/.test(item.url)) { // filter path that will be included in this specific sitemap file
            item.changefreq = 'weekly';
            item.lastmod = new Date();
            item.priority = 0.9; // define specific properties for this filtered path
            return item;
          }
        },
        'glossary': (item) => {
          if (/glossary/.test(item.url)) {
            item.changefreq = 'weekly';
            item.lastmod = new Date();
            item.priority = 0.7;
            return item;
          }
        }
  
        // the rest of the path will be stored in `sitemap-pages.0.xml`
      },
    }),
  ],
  
  

v3.6.1

Compare Source

Patch Changes

• #​15033 dd06779 Thanks @​florian-lefebvre! - Updates how routes are retrieved to avoid relying on a deprecated API

withastro/astro (@​astrojs/vue)

v5.1.4

Compare Source

Patch Changes

• #​15016 12eb4cd Thanks @​rahuld109! - Adds support for arbitrary HTML attributes on Vue components

v5.1.3

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.

v5.1.2

Compare Source

Patch Changes

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

---

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.