build(deps): bump the astro-packages group with 3 updates

[dependabot]

Bumps the astro-packages group with 3 updates: @astrojs/mdx, @astrojs/sitemap and astro.

Updates @astrojs/mdx from 4.3.4 to 4.3.6

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​4.3.6

Patch Changes

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

@​astrojs/mdx@​4.3.5

Patch Changes

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

Changelog

Sourced from @​astrojs/mdx's changelog.

4.3.6

Patch Changes

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

4.3.5

Patch Changes

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

Commits

• 29ff12f [ci] release (#14416)
• aa7bebd [ci] release (#14295)
• c24a8f4 fix(vite): update vite to fix CVE (#14326)
• 42a2cc5 fix(deps): update astro dependencies (#14307)
• bdc8ce2 fix(deps): update astro dependencies (#14305)
• See full diff in compare view

Updates @astrojs/sitemap from 3.5.1 to 3.6.0

Release notes

Sourced from @​astrojs/sitemap's releases.

@​astrojs/sitemap@​3.6.0

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>
  

Changelog

Sourced from @​astrojs/sitemap's changelog.

3.6.0

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>
  

Commits

• 3c14936 [ci] release (#14342)
• ccf0c14 [ci] format
• bedc31b feat(sitemap): add namespaces configuration option (#14285)
• 1a44823 fix(deps): update all non-major dependencies (#13700)
• See full diff in compare view

Updates astro from 5.13.5 to 5.14.1

Release notes

Sourced from astro's releases.

astro@5.14.1

Patch Changes

• #14440 a3e16ab Thanks @​florian-lefebvre! - Fixes a case where the URLs generated by the experimental Fonts API would be incorrect in dev

astro@5.14.0

Minor Changes

• #13520 a31edb8 Thanks @​openscript! - Adds a new property routePattern available to GetStaticPathsOptions

  This provides the original, dynamic segment definition in a routing file path (e.g. /[...locale]/[files]/[slug]) from the Astro render context that would not otherwise be available within the scope of getStaticPaths(). This can be useful to calculate the params and props for each page route.

  For example, you can now localize your route segments and return an array of static paths by passing routePattern to a custom getLocalizedData() helper function. The params object will be set with explicit values for each route segment (e.g. locale, files, and slug). Then, these values will be used to generate the routes and can be used in your page template via Astro.params.

  // src/pages/[...locale]/[files]/[slug].astro
  import { getLocalizedData } from "../../../utils/i18n"; export async function getStaticPaths({ routePattern
  }) { const response = await fetch('...'); const data = await response.json(); console.log(routePattern);
  // [...locale]/[files]/[slug] // Call your custom helper with routePattern to generate the static
  paths return data.flatMap((file) => getLocalizedData(file, routePattern)); } const { locale, files,
  slug } = Astro.params;

  For more information about this advanced routing pattern, see Astro's routing reference.

• #13651 dcfbd8c Thanks @​ADTC! - Adds a new SvgComponent type

  You can now more easily enforce type safety for your .svg assets by directly importing SVGComponent from astro/types:

  ---
  // src/components/Logo.astro
  import type { SvgComponent } from 'astro/types';
  import HomeIcon from './Home.svg';
  interface Link {
    url: string;
    text: string;
    icon: SvgComponent;
  }
  const links: Link[] = [
    {
      url: '/',
      text: 'Home',
      icon: HomeIcon,
    },
  ];
  ---

... (truncated)

Changelog

Sourced from astro's changelog.

5.14.1

Patch Changes

• #14440 a3e16ab Thanks @​florian-lefebvre! - Fixes a case where the URLs generated by the experimental Fonts API would be incorrect in dev

5.14.0

Minor Changes

• #13520 a31edb8 Thanks @​openscript! - Adds a new property routePattern available to GetStaticPathsOptions

  This provides the original, dynamic segment definition in a routing file path (e.g. /[...locale]/[files]/[slug]) from the Astro render context that would not otherwise be available within the scope of getStaticPaths(). This can be useful to calculate the params and props for each page route.

  For example, you can now localize your route segments and return an array of static paths by passing routePattern to a custom getLocalizedData() helper function. The params object will be set with explicit values for each route segment (e.g. locale, files, and slug). Then, these values will be used to generate the routes and can be used in your page template via Astro.params.

  ---
  // src/pages/[...locale]/[files]/[slug].astro
  import { getLocalizedData } from '../../../utils/i18n';
  export async function getStaticPaths({ routePattern }) {
  const response = await fetch('...');
  const data = await response.json();
  console.log(routePattern); // [...locale]/[files]/[slug]
  // Call your custom helper with routePattern to generate the static paths
  return data.flatMap((file) => getLocalizedData(file, routePattern));
  }
  const { locale, files, slug } = Astro.params;

  For more information about this advanced routing pattern, see Astro's routing reference.

• #13651 dcfbd8c Thanks @​ADTC! - Adds a new SvgComponent type

  You can now more easily enforce type safety for your .svg assets by directly importing SVGComponent from astro/types:

  ---
  // src/components/Logo.astro
  import type { SvgComponent } from 'astro/types';
  import HomeIcon from './Home.svg';
  interface Link {
    url: string;
    text: string;
    icon: SvgComponent;

... (truncated)

Commits

• a759c1f [ci] release (#14442)
• 1f7ec7d fix: changelog code snippet (#14443)
• a3e16ab fix(astro): invalid font url (#14440)
• 47df8f2 [ci] format
• bdcd9e0 docs: Clarification in ResponseSentError cause (#14391)
• b0cffe7 Fix name of new flag in changelog (#14437)
• 731c07d [ci] release (#14434)
• dcfbd8c feat(types): add SvgComponent type and update SVG module declaration (#13651)
• a98ce3c [ci] format
• a31edb8 feat(core): add routePattern to GetStaticPathsOptions (#13520)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions