fix(deps): update astro monorepo (astro) #852

renovate · 2025-08-14T13:11:37Z

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/mdx (source)	`4.3.3` -> `4.3.8`
@astrojs/sitemap (source)	`3.4.2` -> `3.6.0`
astro (source)	`5.12.9` -> `5.15.1`

Release Notes

withastro/astro (@astrojs/mdx)

`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

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 '@&#8203;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 '@&#8203;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.

withastro/astro (astro)

`v5.15.1`

Compare Source

Patch Changes

#14612 18552c7 Thanks @ematipico! - Fixes a regression introduced in Astro v5.14.7 that caused ?url imports to not work correctly. This release reverts #14142.

`v5.15.0`

Compare Source

Minor Changes

#14543 9b3241d Thanks @matthewp! - Adds two new adapter configuration options assetQueryParams and internalFetchHeaders to the Adapter API.

Official and community-built adapters can now use client.assetQueryParams to specify query parameters that should be appended to asset URLs (CSS, JavaScript, images, fonts, etc.). The query parameters are automatically appended to all generated asset URLs during the build process.

Adapters can also use client.internalFetchHeaders to specify headers that should be included in Astro's internal fetch calls (Actions, View Transitions, Server Islands, Prefetch).

This enables features like Netlify's skew protection, which requires the deploy ID to be sent with both internal requests and asset URLs to ensure client and server versions match during deployments.
#14489 add4277 Thanks @dev-shetty! - Adds a new Copy to Clipboard button to the error overlay stack trace.

When an error occurs in dev mode, you can now copy the stack trace with a single click to more easily share it in a bug report, a support thread, or with your favorite LLM.
#14564 5e7cebb Thanks @florian-lefebvre! - Updates astro add cloudflare to scaffold more configuration files

Running astro add cloudflare will now emit wrangler.jsonc and public/.assetsignore, allowing your Astro project to work out of the box as a worker.

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
#13826 8079482 Thanks @florian-lefebvre! - Adds the option to specify in the preload directive which weights, styles, or subsets to preload for a given font family when using the experimental Fonts API:

`v5.14.8`

Compare Source

Patch Changes

#14590 577d051 Thanks @matthewp! - Fixes image path resolution in content layer collections to support bare filenames. The image() helper now normalizes bare filenames like "cover.jpg" to relative paths "./cover.jpg" for consistent resolution behavior between markdown frontmatter and JSON content collections.

`v5.14.7`

Compare Source

Patch Changes

#14582 7958c6b Thanks @florian-lefebvre! - Fixes a regression that caused Actions to throw errors while loading
#14567 94500bb Thanks @matthewp! - Fixes the actions endpoint to return 404 for non-existent actions instead of throwing an unhandled error
#14566 946fe68 Thanks @matthewp! - Fixes handling malformed cookies gracefully by returning the unparsed value instead of throwing

When a cookie with an invalid value is present (e.g., containing invalid URI sequences), Astro.cookies.get() now returns the raw cookie value instead of throwing a URIError. This aligns with the behavior of the underlying cookie package and prevents crashes when manually-set or corrupted cookies are encountered.
#14142 73c5de9 Thanks @P4tt4te! - Updates handling of CSS for hydrated client components to prevent duplicates
#14576 2af62c6 Thanks @aprici7y! - Fixes a regression that caused Astro.site to always be undefined in getStaticPaths()

`v5.14.6`

Compare Source

Patch Changes

#14562 722bba0 Thanks @erbierc! - Fixes a bug where the behavior of the "muted" HTML attribute was inconsistent with that of other attributes.
#14538 51ebe6a Thanks @florian-lefebvre! - Improves how Actions are implemented
#14548 6cdade4 Thanks @ascorbic! - Removes support for the maxAge property in cacheHint objects returned by live loaders.

⚠️ Breaking change for experimental live content collections only

Feedback showed that this did not make sense to set at the loader level, since the loader does not know how long each individual entry should be cached for.

If your live loader returns cache hints with maxAge, you need to remove this property:

return {
  entries: [...],
  cacheHint: {
    tags: ['my-tag'],
-   maxAge: 60,
    lastModified: new Date(),
  },
};

The cacheHint object now only supports tags and lastModified properties. If you want to set the max age for a page, you can set the headers manually:

`v5.14.5`

Compare Source

Patch Changes

#14525 4f55781 Thanks @penx! - Fixes defineLiveCollection() types
#14441 62ec8ea Thanks @upsuper! - Updates redirect handling to be consistent across static and server output, aligning with the behavior of other adapters.

Previously, the Node.js adapter used default HTML files with meta refresh tags when in static output. This often resulted in an extra flash of the page on redirect, while also not applying the proper status code for redirections. It's also likely less friendly to search engines.

This update ensures that configured redirects are always handled as HTTP redirects regardless of output mode, and the default HTML files for the redirects are no longer generated in static output. It makes the Node.js adapter more consistent with the other official adapters.

No change to your project is required to take advantage of this new adapter functionality. It is not expected to cause any breaking changes. However, if you relied on the previous redirecting behavior, you may need to handle your redirects differently now. Otherwise you should notice smoother redirects, with more accurate HTTP status codes, and may potentially see some SEO gains.
#14506 ec3cbe1 Thanks @abdo-spices! - Updates the <Font /> component so that preload links are generated after the style tag, as recommended by capo.js

`v5.14.4`

Compare Source

Patch Changes

#14509 7e04caf Thanks @ArmandPhilippot! - Fixes an error in the docs that specified an incorrect version for the security.allowedDomains release.

`v5.14.3`

Compare Source

Patch Changes

#14505 28b2a1d Thanks @matthewp! - Fixes Cannot set property manifest error in test utilities by adding a protected setter for the manifest property
#14235 c4d84bb Thanks @toxeeec! - Fixes a bug where the "tap" prefetch strategy worked only on the first clicked link with view transitions enabled

`v5.14.1`

Compare Source

Patch Changes

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

`v5.14.0`

Compare Source

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.

`v5.13.11`

Compare Source

Patch Changes

#14409 250a595 Thanks @louisescher! - Fixes an issue where astro info would log errors to console in certain cases.
#14398 a7df80d Thanks @idawnlight! - Fixes an unsatisfiable type definition when calling addServerRenderer on an experimental container instance
#13747 120866f Thanks @jp-knj! - Adds automatic request signal abortion when the underlying socket closes in the Node.js adapter

The Node.js adapter now automatically aborts the request.signal when the client connection is terminated. This enables better resource management and allows applications to properly handle client disconnections through the standard AbortSignal API.
#14428 32a8acb Thanks @drfuzzyness! - Force sharpService to return a Uint8Array if Sharp returns a SharedArrayBuffer
#14411 a601186 Thanks @GameRoMan! - Fixes relative links to docs that could not be opened in the editor.

Patch Changes

#14402 54dcd04 Thanks @FredKSchott! - Removes warning that caused unexpected console spam when using Bun

`v5.13.8`

Compare Source

Patch Changes

#14300 bd4a70b Thanks @louisescher! - Adds Vite version & integration versions to output of astro info
#14341 f75fd99 Thanks @delucis! - Fixes support for declarative Shadow DOM when using the <ClientRouter> component
#14350 f59581f Thanks @ascorbic! - Improves error reporting for content collections by adding logging for configuration errors that had previously been silently ignored. Also adds a new error that is thrown if a live collection is used in content.config.ts rather than live.config.ts.
#14343 13f7d36 Thanks @florian-lefebvre! - Fixes a regression in non node runtimes

`v5.13.7`

Compare Source

Patch Changes

#14330 72e14ab Thanks @ascorbic! - Removes pinned package that is no longer needed.
#14335 17c7b03 Thanks @florian-lefebvre! - Bumps sharp minimal version to 0.34.0

`v5.13.6`

Compare Source

Patch Changes

#14294 e005855 Thanks @martrapp! - Restores the ability to use Google Analytics History change trigger with the <ClientRouter />.
#14326 c24a8f4 Thanks @jsparkdev! - Updates vite version to fix CVE
#14108 218e070 Thanks @JusticeMatthew! - Updates dynamic route split regex to avoid infinite retries/exponential complexity
#14327 c1033be Thanks @ascorbic! - Pins simple-swizzle to avoid compromised version

`v5.13.5`

Compare Source

Patch Changes

#14286 09c5db3 Thanks @ematipico! - BREAKING CHANGES only to the experimental CSP feature

The following runtime APIs of the Astro global have been renamed:
- Astro.insertDirective to Astro.csp.insertDirective
- Astro.insertStyleResource to Astro.csp.insertStyleResource
- Astro.insertStyleHash to Astro.csp.insertStyleHash
- Astro.insertScriptResource to Astro.csp.insertScriptResource
- Astro.insertScriptHash to Astro.csp.insertScriptHash
The following runtime APIs of the APIContext have been renamed:
- ctx.insertDirective to ctx.csp.insertDirective
- ctx.insertStyleResource to ctx.csp.insertStyleResource
- ctx.insertStyleHash to ctx.csp.insertStyleHash
- ctx.insertScriptResource to ctx.csp.insertScriptResource
- ctx.insertScriptHash to ctx.csp.insertScriptHash
#14283 3224637 Thanks @ematipico! - Fixes an issue where CSP headers were incorrectly injected in the development server.
#14275 3e2f20d Thanks @florian-lefebvre! - Adds support for experimental CSP when using experimental fonts

Experimental fonts now integrate well with experimental CSP by injecting hashes for the styles it generates, as well as font-src directives.

No action is required to benefit from it.
#14280 4b9fb73 Thanks @ascorbic! - Fixes a bug that caused cookies to not be correctly set when using middleware sequences
#14276 77281c4 Thanks @ArmandPhilippot! - Adds a missing export for resolveSrc, a documented image services utility.

`v5.13.4`

Compare Source

Patch Changes

#14260 86a1e40 Thanks @jp-knj! - Fixes Astro.url.pathname to respect trailingSlash: 'never' configuration when using a base path. Previously, the root path with a base would incorrectly return /base/ instead of /base when trailingSlash was set to 'never'.
#14248 e81c4bd Thanks @julesyoungberg! - Fixes a bug where actions named 'apply' do not work due to being a function prototype method.

`v5.13.3`

Compare Source

Patch Changes

#14239 d7d93e1 Thanks @wtchnm! - Fixes a bug where the types for the live content collections were not being generated correctly in dev mode
#14221 eadc9dd Thanks @delucis! - Fixes JSON schema support for content collections using the file() loader
#14229 1a9107a Thanks @jonmichaeldarby! - Ensures Astro.currentLocale returns the correct locale during SSG for pages that use a locale param (such as [locale].astro or [locale]/index.astro, which produce [locale].html)

`v5.13.2`

Compare Source

Patch Changes

4d16de7 Thanks @ematipico! - Improves the detection of remote paths in the _image endpoint. Now href parameters that start with // are considered remote paths.
Updated dependencies [4d16de7]:
- @astrojs/internal-helpers@0.7.2
- @astrojs/markdown-remark@6.3.6

`v5.13.1`

Compare Source

Patch Changes

#14409 250a595 Thanks @louisescher! - Fixes an issue where astro info would log errors to console in certain cases.
#14398 a7df80d Thanks @idawnlight! - Fixes an unsatisfiable type definition when calling addServerRenderer on an experimental container instance
#13747 120866f Thanks @jp-knj! - Adds automatic request signal abortion when the underlying socket closes in the Node.js adapter

The Node.js adapter now automatically aborts the request.signal when the client connection is terminated. This enables better resource management and allows applications to properly handle client disconnections through the standard AbortSignal API.
#14428 32a8acb Thanks @drfuzzyness! - Force sharpService to return a Uint8Array if Sharp returns a SharedArrayBuffer
#14411 a601186 Thanks @GameRoMan! - Fixes relative links to docs that could not be opened in the editor.

`v5.13.0`

Compare Source

Minor Changes

#14173 39911b8 Thanks @florian-lefebvre! - Adds an experimental flag staticImportMetaEnv to disable the replacement of import.meta.env values with process.env calls and their coercion of environment variable values. This supersedes the rawEnvValues experimental flag, which is now removed.

Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.

However, you can still access environment variables through process.env and import.meta.env directly when needed. This was the only way to use environment variables in Astro before astro:env was added in Astro 5.0, and Astro's default handling of import.meta.env includes some logic that was only needed for earlier versions of Astro.

The experimental.staticImportMetaEnv flag updates the behavior of import.meta.env to align with Vite's handling of environment variables and for better ease of use with Astro's current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.

Currently, non-public import.meta.env environment variables are replaced by a reference to process.env. Additionally, Astro may also convert the value type of your environment variables used through import.meta.env, which can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

The experimental.staticImportMetaEnv flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any import.meta.env environment variables with a process.env call, nor will it coerce values.

To enable this feature, add the experimental flag in your Astro config and remove rawEnvValues if it was enabled:
```
// astro.config.mjs
import { defineConfig } from "astro/config";

export default defineConfig({
+  experimental: {
+    staticImportMetaEnv: true
-    rawEnvValues: false
+  }
});
```

Updating your project

If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:

// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.ENABLED;
+ const enabled: boolean = import.meta.env.ENABLED === "true";

If you were relying on the transformation into process.env calls, you may need to update your project code to apply it manually:

// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.DB_PASSWORD;
+ const enabled: boolean = process.env.DB_PASSWORD;

You may also need to update types:

// src/env.d.ts
interface ImportMetaEnv {
  readonly PUBLIC_POKEAPI: string;
-  readonly DB_PASSWORD: string;
-  readonly ENABLED: boolean;
+  readonly ENABLED: string;
}

interface ImportMeta {
  readonly env: ImportMetaEnv;
}

+ namespace NodeJS {
+  interface ProcessEnv {
+    DB_PASSWORD: string;
+  }
+ }

See the experimental static import.meta.env documentation for more information about this feature. You can learn more about using environment variables in Astro, including astro:env, in the environment variables documentation.

#14122 41ed3ac Thanks @ascorbic! - Adds experimental support for automatic Chrome DevTools workspace folders

This feature allows you to edit files directly in the browser and have those changes reflected in your local file system via a connected workspace folder. This allows you to apply edits such as CSS tweaks without leaving your browser tab!

With this feature enabled, the Astro dev server will automatically configure a Chrome DevTools workspace for your project. Your project will then appear as a workspace source, ready to connect. Then, changes that you make in the "Sources" panel are automatically saved to your project source code.

To enable this feature, add the experimental flag chromeDevtoolsWorkspace to your Astro config:
```
// astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    chromeDevtoolsWorkspace: true,
  },
});
```
See the experimental Chrome DevTools workspace feature documentation for more information.

Configuration

📅 Schedule: 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.

netlify · 2025-08-14T13:11:42Z

✅ Deploy Preview for prismlauncher-astro ready!

Name	Link
🔨 Latest commit	`ece3386`
🔍 Latest deploy log	https://app.netlify.com/projects/prismlauncher-astro/deploys/68fa665ccf90ef000999c499
😎 Deploy Preview	https://deploy-preview-852--prismlauncher-astro.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

cloudflare-workers-and-pages · 2025-08-14T13:12:46Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	prismlauncher	`ece3386`	Oct 23 2025, 05:31 PM

renovate bot force-pushed the renovate/astro-astro-monorepo branch 2 times, most recently from da14ba5 to e21e582 Compare August 15, 2025 18:28

renovate bot force-pushed the renovate/astro-astro-monorepo branch 2 times, most recently from ccd0e9a to 75f107a Compare August 27, 2025 10:41

renovate bot force-pushed the renovate/astro-astro-monorepo branch from 75f107a to 3ca5e5b Compare August 31, 2025 09:13

renovate bot force-pushed the renovate/astro-astro-monorepo branch 2 times, most recently from 663f6d6 to 4ac77c5 Compare September 9, 2025 17:59

renovate bot force-pushed the renovate/astro-astro-monorepo branch 3 times, most recently from 64cbc9e to c810f8c Compare September 22, 2025 09:52

renovate bot force-pushed the renovate/astro-astro-monorepo branch 3 times, most recently from a90ca94 to 1cec5fe Compare September 26, 2025 12:06

renovate bot force-pushed the renovate/astro-astro-monorepo branch 3 times, most recently from 86ed67e to e178667 Compare October 14, 2025 16:47

renovate bot force-pushed the renovate/astro-astro-monorepo branch 5 times, most recently from 3812291 to 1da57c9 Compare October 23, 2025 13:41

fix(deps): update astro monorepo

ece3386

renovate bot force-pushed the renovate/astro-astro-monorepo branch from 1da57c9 to ece3386 Compare October 23, 2025 17:31

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(deps): update astro monorepo (astro) #852

fix(deps): update astro monorepo (astro) #852

Uh oh!

renovate bot commented Aug 14, 2025 •

edited

Loading

Uh oh!

netlify bot commented Aug 14, 2025 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages bot commented Aug 14, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

fix(deps): update astro monorepo (astro) #852

Are you sure you want to change the base?

fix(deps): update astro monorepo (astro) #852

Uh oh!

Conversation

renovate bot commented Aug 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

⚠️ Breaking change for experimental live content collections only

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Updating your project

Configuration

Uh oh!

netlify bot commented Aug 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for prismlauncher-astro ready!

Uh oh!

cloudflare-workers-and-pages bot commented Aug 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Aug 14, 2025 •

edited

Loading

netlify bot commented Aug 14, 2025 •

edited

Loading

cloudflare-workers-and-pages bot commented Aug 14, 2025 •

edited

Loading