chore(deps): update astro monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/mdx (source)	4.2.6 -> 4.3.7
@astrojs/sitemap (source)	3.4.0 -> 3.6.0

---

Release Notes

withastro/astro (@​astrojs/mdx)

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

withastro/astro (@​astrojs/sitemap)

v3.6.0

Compare Source

Minor Changes

• #​14285 bedc31b Thanks @​jdcolombo! - Adds a new configuration option namespaces for more control over XML namespaces used in sitemap generation

  Excluding unused namespaces can help create cleaner, more focused sitemaps that are faster for search engines to parse and use less bandwidth. If your site doesn't have news content, videos, or multiple languages, you can exclude those namespaces to reduce XML bloat.

  The namespaces option allows you to configure news, xhtml, image, and video namespaces independently. All namespaces are enabled by default for backward compatibility and no change to existing projects is necessary. But now, you can choose to streamline your XML and avoid unnecessary code.

  For example, to exclude the video namespace from your sitemap, set video: false in your configuration:

  // astro.config.mjs
  import { sitemap } from '@​astrojs/sitemap';
  
  export default {
    integrations: [
      sitemap({
        namespaces: {
          video: false,
          // other namespaces remain enabled by default
        }
      })
    ]
  };
  

  The generated XML will not include the xmlns:video namespace:

  <?xml version="1.0" encoding="UTF-8"?>
  <urlset
    xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
    xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"
    xmlns:xhtml="http://www.w3.org/1999/xhtml"
    xmlns:image="http://www.google.com/schemas/sitemap-image/1.1"
  >
    <!-- ... -->
  </urlset>
  

v3.5.1

Compare Source

Patch Changes

• #​14233 896886c Thanks @​gouravkhunger! - Fixes the issue with the option lastmod where if it is defined it applies correctly to <url> entries in each sitemap-${i}.xml file but not the <sitemap> entries in the root sitemap-index.xml file.

v3.5.0

Compare Source

Minor Changes

• #​13682 5824b32 Thanks @​gouravkhunger! - Adds a customSitemaps option to include extra sitemaps in the sitemap-index.xml file generated by Astro.

  This is useful for multi-framework setups on the same domain as your Astro site (example.com), such as a blog at example.com/blog whose sitemap is generated by another framework.

  The following example shows configuring your Astro site to include sitemaps for an externally-generated blog and help center along with the generated sitemap entries in sitemap-index.xml:

  Example:

  import { defineConfig } from 'astro/config';
  import sitemap from '@​astrojs/sitemap';
  
  export default defineConfig({
    site: 'https://example.com',
    integrations: [
      sitemap({
        customSitemaps: [
          'https://example.com/blog/sitemap.xml',
          'https://example.com/helpcenter/sitemap.xml',
        ],
      }),
    ],
  });

  Learn more in the @astrojs/sitemap configuration documentation.

v3.4.2

Compare Source

Patch Changes

• #​14127 2309ada Thanks @​florian-lefebvre! - Upgrades zod

v3.4.1

Compare Source

Patch Changes

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.