chore(deps): update astro monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/cloudflare (source)	9.1.0 -> 9.2.1
@astrojs/mdx (source)	2.2.0 -> 2.3.1
@astrojs/rss (source)	4.0.5 -> 4.0.14
@astrojs/sitemap (source)	3.1.1 -> 3.6.0
@astrojs/solid-js (source)	4.0.1 -> 4.4.4

---

Release Notes

withastro/astro (@​astrojs/cloudflare)

v9.2.1

Patch Changes

• #​204 826bb4fe1fa2a95a38397f927210cdf37079c38a Thanks @​dario-piotrowicz! - Fixes a typo for a Cloudflare runtime .dev.vars warning

v9.2.0

Minor Changes

• #​192 256b7024624ab45d5087d774cb4c30b117f1636a Thanks @​alexanderniebuhr! - Prepares for major breaking changes to adapter configuration in the upcoming v10 release.

  (Full documentation to help you migrate your project to the upgraded Cloudflare adapter will be provided with the release of v10.0.)

  Deprecates the following adapter configuration options (to be removed entirely in v10):

  • mode: All projects will deploy to Cloudflare pages using advanced mode (the previous default setting). This is no longer a configurable option. Cloudflare Functions will no longer be supported. If you were using mode: 'directory', please migrate to Astro Endpoints.
  • functionPerRoute: Discontinued due to Cloudflare's single execution context approach. You will no longer have the option to compile a separate bundle for each page.
  • routes.strategy: Projects will use the auto-generated _route.json for route management unless you provide your own public/_routes.json. This change aims to eliminate confusion and promote consistency.
  • routes.include: Will be replaced by a new routes.extend.include option to allow you to include additional routes.
  • routes.exclude: Will be replaced by a new routes.extend.exclude option to allow you to exclude additional routes.
  • runtime: Local runtime bindings will be configured in wrangler.toml at the root of your project as described in the adapters documentation. You will no longer configure these directly in the adapter configuration. A new platformProxy setting will be introduced to enable and configure the platformProxy (local runtime) provided by wrangler.

  These changes are part of ongoing efforts to streamline functionality, improve performance, and align with best practices and platform capabilities.

  We strongly recommend upgrading to v10 upon its release. To ensure a smooth migration, we commit to at least 4 weeks of additional maintenance for v9 following the release of v10. During this period, we will actively assist with migration efforts to ensure that all users can transition without major issues.

withastro/astro (@​astrojs/mdx)

v2.3.1

Compare Source

Patch Changes

• #​10754 3e7a12c8532411e580fcfdb8445cad8fc8499291 Thanks @​rishi-raj-jain! - Fixes an issue where images in MDX required a relative specifier (e.g. ./)

  Now, you can use the standard ![](img.png) syntax in MDX files for images colocated in the same folder: no relative specifier required!

  There is no need to update your project; your existing images will still continue to work. However, you may wish to remove any relative specifiers from these MDX images as they are no longer necessary:

  - ![A cute dog](./dog.jpg)
  + ![A cute dog](dog.jpg)
  <!-- This dog lives in the same folder as my article! -->

• #​10770 88ee63a3ba4488c60348cb821034e6d4a057efd0 Thanks @​bluwy! - Removes internal MDX processor on buildEnd to free up memory

v2.3.0

Compare Source

Minor Changes

• #​10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @​ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

  This change is in line with Astro's Node.js support policy.

Patch Changes

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

v2.2.4

Compare Source

Patch Changes

• #​10673 db7f9c87035a0de780536d95cdd9facff00c3c08 Thanks @​bluwy! - Removes unnecessary internal recmaInjectImportMetaEnv plugin

v2.2.3

Compare Source

Patch Changes

• Updated dependencies [2cf116f80cb5e421ab5cc5eb4a654e7b78c1b8de, 374efcdff9625ca43309d89e3b9cfc9174351512]:
  • @​astrojs/markdown-remark@​5.0.0

v2.2.2

Compare Source

Patch Changes

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

v2.2.1

Compare Source

Patch Changes

• Updated dependencies [19e42c368184013fc30d1e46753b9e9383bb2bdf]:
  • @​astrojs/markdown-remark@​4.3.1

withastro/astro (@​astrojs/rss)

v4.0.14

Compare Source

Patch Changes

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

v4.0.13

Compare Source

Patch Changes

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

v4.0.12

Compare Source

Patch Changes

• #​13867 c947c28 Thanks @​Adriel-M! - Fixes a missing type attribute when providing a XSLT stylesheet

v4.0.11

Compare Source

Patch Changes

• #​12829 ebe2aa9 Thanks @​SapphicMoe! - Revert incorrect Content-Type header applied for RSS XML file

v4.0.10

Compare Source

Patch Changes

• #​12644 5b9b618 Thanks @​kunyan! - Sends the standard RSS content type response header, with UTF-8 charset

v4.0.9

Compare Source

Patch Changes

• #​12157 925cff3 Thanks @​bholmesdev! - Improves README configuration reference.

v4.0.8

Compare Source

Patch Changes

• #​12137 50dd88b Thanks @​ArmandPhilippot! - Fixes an error that occurred when the optional pubDate property was missing in an item.

• #​12137 50dd88b Thanks @​ArmandPhilippot! - Fixes an error where docs incorrectly stated the title, link and pubDate properties of RSS items was required.

v4.0.7

Compare Source

Patch Changes

• #​11299 8ce66f2 Thanks @​ematipico! - Fixes an issue where the pagesGlobToRssItems returned an incorrect type for items

v4.0.6

Compare Source

Patch Changes

• #​11050 841df1f Thanks @​mingjunlu! - Fixes an issue where trailing slash is not removed even if the trailingSlash option is set to false.

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.

v3.4.0

Compare Source

Minor Changes

• #​13753 90293de Thanks @​mattyoho! - Customize the filenames of sitemap XML files generated by the @astro/sitemap integration by setting filenameBase in the integration configuration settings. This may be useful when deploying an Astro site at a path on a domain with preexisting sitemap files.

  Generated sitemap files will appear at /sitemap-0.xml and /sitemap-index.xml by default, which may conflict with preexisting files. Set filenameBase to a custom value to avoid that if so:

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

  This will yield sitemap and index files as https://example.com/astronomy-sitemap-0.xml and https://example.com/astronomy-sitemap-index.xml.

v3.3.1

Patch Changes

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

v3.3.0

Minor Changes

• #​13448 91c9503 Thanks @​ematipico! - Add support for XSL in sitemap-index.xml

v3.2.1

Compare Source

Patch Changes

• #​12156 07754f5 Thanks @​mingjunlu! - Adds missing xslURL property to SitemapOptions type.

v3.2.0

Compare Source

Minor Changes

• #​11485 fbe1bc5 Thanks @​sondr3! - Adds new xslURL option to enable styling of sitemaps

v3.1.6

Compare Source

Patch Changes

• #​11263 7d59750 Thanks @​wackbyte! - Refactor to use Astro's integration logger for logging

v3.1.5

Compare Source

Patch Changes

• #​10779 cefeadf Thanks @​adrianlyjak! - Fixes false positives for status code routes like 404 and 500 when generating sitemaps.

v3.1.4

Compare Source

Patch Changes

• #​10772 0e22462d1534afc8f7bb6782f86db680c7a5f245 Thanks @​gislerro! - Fixes an issue where the root url does not follow the trailingSlash config option

v3.1.3

Compare Source

Patch Changes

• #​10795 1ce22881c657becf0397b83ac393fb5d2399104c Thanks @​bluwy! - Improves performance when generating the sitemap data

v3.1.2

Compare Source

Patch Changes

• #​10557 5f7e9c47e01116f6ec74b33770f480404680956a Thanks @​mingjunlu! - Fixes an issue where the base path is missing in sitemap-index.xml.

withastro/astro (@​astrojs/solid-js)

v4.4.4

Compare Source

Patch Changes

• #​12481 8a46e80 Thanks @​marbrex! - Resolve vite peer dependency problem for strict package managers like Yarn in PnP mode.

v4.4.3

Compare Source

Patch Changes

• #​12364 9fc2ab8 Thanks @​jdtjenkins! - Handles checking Svelte 5 component functions to avoid processing them as Solid components

v4.4.2

Compare Source

Patch Changes

• #​11998 082f450 Thanks @​johannesspohr! - Fix view transition state persistence

v4.4.1

Compare Source

Patch Changes

• #​11624 7adb350 Thanks @​bluwy! - Prevents throwing errors when checking if a component is a Solid component in runtime

v4.4.0

Compare Source

Minor Changes

• #​11234 4385bf7 Thanks @​ematipico! - Adds a new function called addServerRenderer to the Container API. Use this function to manually store renderers inside the instance of your container.

  This new function should be preferred when using the Container API in environments like on-demand pages:

  import type { APIRoute } from 'astro';
  import { experimental_AstroContainer } from 'astro/container';
  import reactRenderer from '@​astrojs/react/server.js';
  import vueRenderer from '@​astrojs/vue/server.js';
  import ReactComponent from '../components/button.jsx';
  import VueComponent from '../components/button.vue';
  
  // MDX runtime is contained inside the Astro core
  import mdxRenderer from 'astro/jsx/server.js';
  
  // In case you need to import a custom renderer
  import customRenderer from '../renderers/customRenderer.js';
  
  export const GET: APIRoute = async (ctx) => {
    const container = await experimental_AstroContainer.create();
    container.addServerRenderer({ renderer: reactRenderer });
    container.addServerRenderer({ renderer: vueRenderer });
    container.addServerRenderer({ renderer: customRenderer });
    // You can pass a custom name too
    container.addServerRenderer({
      name: 'customRenderer',
      renderer: customRenderer,
    });
    const vueComponent = await container.renderToString(VueComponent);
    return await container.renderToResponse(Component);
  };

v4.3.0

Compare Source

Minor Changes

• #​11144 803dd80 Thanks @​ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.

  import { experimental_AstroContainer as AstroContainer } from 'astro/container';
  import ReactWrapper from '../src/components/ReactWrapper.astro';
  import { loadRenderers } from 'astro:container';
  import { getContainerRenderer } from '@​astrojs/react';
  
  test('ReactWrapper with react renderer', async () => {
    const renderers = await loadRenderers([getContainerRenderer()]);
    const container = await AstroContainer.create({
      renderers,
    });
    const result = await container.renderToString(ReactWrapper);
  
    expect(result).toContain('Counter');
    expect(result).toContain('Count: <!-- -->5');
  });

v4.2.0

Compare Source

Minor Changes

• #​10937 7179930 Thanks @​florian-lefebvre! - Adds a devtools option

  You can enable the official Solid Devtools while working in development mode by setting devtools: true in your solid() integration config and adding solid-devtools to your project dependencies:

  npm install solid-devtools

v4.1.0

Compare Source

Minor Changes

• #​10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @​ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

  This change is in line with Astro's Node.js support policy.

---

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.

[cloudflare-workers-and-pages]

Deploying enpitsulin-xyz with    Cloudflare Pages

Latest commit:	f40ceb5
Status:	🚫  Build failed.

View logs