Update astro monorepo #42

renovate-bot · 2025-07-19T00:02:23Z

renovate-bot commented

2025-07-19 00:02:23 +00:00

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/mdx (source)	`4.3.0` -> `4.3.1`
astro (source)	`5.11.2` -> `5.12.0`

Release Notes

withastro/astro (@astrojs/mdx)

`v4.3.1`

Compare Source

Patch Changes

Updated dependencies [6bd5f75]:
- @astrojs/markdown-remark@6.3.3

withastro/astro (astro)

`v5.12.0`

Compare Source

Minor Changes

#13971 fe35ee2 Thanks @adamhl8! - Adds an experimental flag rawEnvValues to disable coercion of import.meta.env values (e.g. converting strings to other data types) that are populated from process.env

Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type.

However, Astro also converts your environment variables used through import.meta.env in some cases, and this 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.rawEnvValues flag disables coercion of import.meta.env values that are populated from process.env, allowing you to use the raw value.

To enable this feature, add the experimental flag in your Astro config:
```
import { defineConfig } from "astro/config"

export default defineConfig({
+  experimental: {
+    rawEnvValues: true,
+  }
})
```
If you were relying on this coercion, you may need to update your project code to apply it manually:
```
- const enabled: boolean = import.meta.env.ENABLED
+ const enabled: boolean = import.meta.env.ENABLED === "true"
```
See the experimental raw environment variables reference docs for more information.
#13941 6bd5f75 Thanks @aditsachde! - Adds support for TOML files to Astro's built-in glob() and file() content loaders.

In Astro 5.2, Astro added support for using TOML frontmatter in Markdown files instead of YAML. However, if you wanted to use TOML files as local content collection entries themselves, you needed to write your own loader.

Astro 5.12 now directly supports loading data from TOML files in content collections in both the glob() and the file() loaders.

If you had added your own TOML content parser for the file() loader, you can now remove it as this functionality is now included:
```
// src/content.config.ts
import { defineCollection } from "astro:content";
import { file } from "astro/loaders";
- import { parse as parseToml } from "toml";
const dogs = defineCollection({
-  loader: file("src/data/dogs.toml", { parser: (text) => parseToml(text) }),
+ loader: file("src/data/dogs.toml")
  schema: /* ... */
})
```
Note that TOML does not support top-level arrays. Instead, the file() loader considers each top-level table to be an independent entry. The table header is populated in the id field of the entry object.

See Astro's content collections guide for more information on using the built-in content loaders.

Patch Changes

Updated dependencies [6bd5f75]:
- @astrojs/markdown-remark@6.3.3

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 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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [@astrojs/mdx](https://docs.astro.build/en/guides/integrations-guide/mdx/) ([source](https://github.com/withastro/astro/tree/HEAD/packages/integrations/mdx)) | [`4.3.0` -> `4.3.1`](https://renovatebot.com/diffs/npm/@astrojs%2fmdx/4.3.0/4.3.1) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@astrojs%2fmdx/4.3.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@astrojs%2fmdx/4.3.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@astrojs%2fmdx/4.3.0/4.3.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@astrojs%2fmdx/4.3.0/4.3.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [astro](https://astro.build) ([source](https://github.com/withastro/astro/tree/HEAD/packages/astro)) | [`5.11.2` -> `5.12.0`](https://renovatebot.com/diffs/npm/astro/5.11.2/5.12.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/astro/5.12.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/astro/5.12.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/astro/5.11.2/5.12.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/astro/5.11.2/5.12.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>withastro/astro (@astrojs/mdx)</summary> ### [`v4.3.1`](https://github.com/withastro/astro/blob/HEAD/packages/integrations/mdx/CHANGELOG.md#431) [Compare Source](https://github.com/withastro/astro/compare/@astrojs/mdx@4.3.0...@astrojs/mdx@4.3.1) ##### Patch Changes - Updated dependencies \[[`6bd5f75`](https://github.com/withastro/astro/commit/6bd5f75806cb4df39d9e4e9b1f2225dcfdd724b0)]: - [@astrojs/markdown-remark](https://github.com/astrojs/markdown-remark)@6.3.3 </details> <details> <summary>withastro/astro (astro)</summary> ### [`v5.12.0`](https://github.com/withastro/astro/blob/HEAD/packages/astro/CHANGELOG.md#5120) [Compare Source](https://github.com/withastro/astro/compare/astro@5.11.2...astro@5.12.0) ##### Minor Changes - [#13971](https://github.com/withastro/astro/pull/13971) [`fe35ee2`](https://github.com/withastro/astro/commit/fe35ee2835997e7e6c3e1975dc6dacfa1052a765) Thanks [@adamhl8](https://github.com/adamhl8)! - Adds an experimental flag `rawEnvValues` to disable coercion of `import.meta.env` values (e.g. converting strings to other data types) that are populated from `process.env` Astro allows you to configure a [type-safe schema for your environment variables](https://docs.astro.build/en/guides/environment-variables/#type-safe-environment-variables), and converts variables imported via `astro:env` into the expected type. However, Astro also converts your environment variables used through `import.meta.env` in some cases, and this 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.rawEnvValues` flag disables coercion of `import.meta.env` values that are populated from `process.env`, allowing you to use the raw value. To enable this feature, add the experimental flag in your Astro config: ```diff import { defineConfig } from "astro/config" export default defineConfig({ + experimental: { + rawEnvValues: true, + } }) ``` If you were relying on this coercion, you may need to update your project code to apply it manually: ```ts diff - const enabled: boolean = import.meta.env.ENABLED + const enabled: boolean = import.meta.env.ENABLED === "true" ``` See the [experimental raw environment variables reference docs](https://docs.astro.build/en/reference/experimental-flags/raw-env-values/) for more information. - [#13941](https://github.com/withastro/astro/pull/13941) [`6bd5f75`](https://github.com/withastro/astro/commit/6bd5f75806cb4df39d9e4e9b1f2225dcfdd724b0) Thanks [@aditsachde](https://github.com/aditsachde)! - Adds support for TOML files to Astro's built-in `glob()` and `file()` content loaders. In Astro 5.2, Astro added support for using TOML frontmatter in Markdown files instead of YAML. However, if you wanted to use TOML files as local content collection entries themselves, you needed to write your own loader. Astro 5.12 now directly supports loading data from TOML files in content collections in both the `glob()` and the `file()` loaders. If you had added your own TOML content parser for the `file()` loader, you can now remove it as this functionality is now included: ```diff // src/content.config.ts import { defineCollection } from "astro:content"; import { file } from "astro/loaders"; - import { parse as parseToml } from "toml"; const dogs = defineCollection({ - loader: file("src/data/dogs.toml", { parser: (text) => parseToml(text) }), + loader: file("src/data/dogs.toml") schema: /* ... */ }) ``` Note that TOML does not support top-level arrays. Instead, the `file()` loader considers each top-level table to be an independent entry. The table header is populated in the `id` field of the entry object. See Astro's [content collections guide](https://docs.astro.build/en/guides/content-collections/#built-in-loaders) for more information on using the built-in content loaders. ##### Patch Changes - Updated dependencies \[[`6bd5f75`](https://github.com/withastro/astro/commit/6bd5f75806cb4df39d9e4e9b1f2225dcfdd724b0)]: - [@astrojs/markdown-remark](https://github.com/astrojs/markdown-remark)@6.3.3 </details> --- ### 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 is behind base branch, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

renovate-bot added the

automerge

dependency

labels 2025-07-19 00:02:23 +00:00

renovate-bot added 1 commit 2025-07-19 00:02:24 +00:00

Update astro monorepo

renovate/stability-days Updates have met minimum release age requirement

Details

test-build / build (pull_request) Successful in 1m25s

Details

c508516d6b

renovate-bot force-pushed renovate/astro-monorepo from c508516d6b to bb4b1f257d