alexlebens/site-profile
1
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Activity

Update astro monorepo #73

Merged
alexlebens merged 1 commits from renovate/astro-monorepo into main 2025-08-17 02:13:39 +00:00
Conversation 0 Commits 1 Files Changed 1 +185 -196
renovate-bot commented 2025-08-16 00:02:01 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/mdx (source) 4.3.3 -> 4.3.4 age adoption passing confidence
@astrojs/node (source) 9.4.0 -> 9.4.2 age adoption passing confidence
@astrojs/sitemap (source) 3.4.2 -> 3.5.0 age adoption passing confidence
astro (source) 5.12.9 -> 5.13.2 age adoption passing confidence

Release Notes

withastro/astro (@​astrojs/mdx)

v4.3.4

Compare Source

Patch Changes
withastro/astro (@​astrojs/node)

v9.4.2

Compare Source

Patch Changes

v9.4.1

Compare Source

Patch Changes
  • 5fc3c59 Thanks @​ematipico! - Fixes a routing bug in standalone mode with trailingSlash set to "always".
withastro/astro (@​astrojs/sitemap)

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.

withastro/astro (astro)

v5.13.2

Compare Source

Patch Changes

v5.13.1

Compare Source

Patch Changes

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: 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.3` -> `4.3.4`](https://renovatebot.com/diffs/npm/@astrojs%2fmdx/4.3.3/4.3.4) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@astrojs%2fmdx/4.3.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@astrojs%2fmdx/4.3.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@astrojs%2fmdx/4.3.3/4.3.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@astrojs%2fmdx/4.3.3/4.3.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [@astrojs/node](https://docs.astro.build/en/guides/integrations-guide/node/) ([source](https://github.com/withastro/astro/tree/HEAD/packages/integrations/node)) | [`9.4.0` -> `9.4.2`](https://renovatebot.com/diffs/npm/@astrojs%2fnode/9.4.0/9.4.2) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@astrojs%2fnode/9.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@astrojs%2fnode/9.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@astrojs%2fnode/9.4.0/9.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@astrojs%2fnode/9.4.0/9.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [@astrojs/sitemap](https://docs.astro.build/en/guides/integrations-guide/sitemap/) ([source](https://github.com/withastro/astro/tree/HEAD/packages/integrations/sitemap)) | [`3.4.2` -> `3.5.0`](https://renovatebot.com/diffs/npm/@astrojs%2fsitemap/3.4.2/3.5.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@astrojs%2fsitemap/3.5.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@astrojs%2fsitemap/3.5.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@astrojs%2fsitemap/3.4.2/3.5.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@astrojs%2fsitemap/3.4.2/3.5.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [astro](https://astro.build) ([source](https://github.com/withastro/astro/tree/HEAD/packages/astro)) | [`5.12.9` -> `5.13.2`](https://renovatebot.com/diffs/npm/astro/5.12.9/5.13.2) | [![age](https://developer.mend.io/api/mc/badges/age/npm/astro/5.13.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/astro/5.13.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/astro/5.12.9/5.13.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/astro/5.12.9/5.13.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>withastro/astro (@&#8203;astrojs/mdx)</summary> ### [`v4.3.4`](https://github.com/withastro/astro/blob/HEAD/packages/integrations/mdx/CHANGELOG.md#434) [Compare Source](https://github.com/withastro/astro/compare/@astrojs/mdx@4.3.3...@astrojs/mdx@4.3.4) ##### Patch Changes - Updated dependencies \[]: - [@&#8203;astrojs/markdown-remark](https://github.com/astrojs/markdown-remark)@&#8203;6.3.6 </details> <details> <summary>withastro/astro (@&#8203;astrojs/node)</summary> ### [`v9.4.2`](https://github.com/withastro/astro/blob/HEAD/packages/integrations/node/CHANGELOG.md#942) [Compare Source](https://github.com/withastro/astro/compare/@astrojs/node@9.4.1...@astrojs/node@9.4.2) ##### Patch Changes - Updated dependencies \[[`4d16de7`](https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820)]: - [@&#8203;astrojs/internal-helpers](https://github.com/astrojs/internal-helpers)@&#8203;0.7.2 ### [`v9.4.1`](https://github.com/withastro/astro/blob/HEAD/packages/integrations/node/CHANGELOG.md#941) [Compare Source](https://github.com/withastro/astro/compare/@astrojs/node@9.4.0...@astrojs/node@9.4.1) ##### Patch Changes - [`5fc3c59`](https://github.com/withastro/astro/commit/5fc3c599cacb0172cc7d8e1202a5f2e8685d7ef2) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixes a routing bug in standalone mode with `trailingSlash` set to `"always"`. </details> <details> <summary>withastro/astro (@&#8203;astrojs/sitemap)</summary> ### [`v3.5.0`](https://github.com/withastro/astro/blob/HEAD/packages/integrations/sitemap/CHANGELOG.md#350) [Compare Source](https://github.com/withastro/astro/compare/@astrojs/sitemap@3.4.2...@astrojs/sitemap@3.5.0) ##### Minor Changes - [#&#8203;13682](https://github.com/withastro/astro/pull/13682) [`5824b32`](https://github.com/withastro/astro/commit/5824b32c5cc5d58c1138e408a05d1be18924c711) Thanks [@&#8203;gouravkhunger](https://github.com/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: ```js 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](https://docs.astro.build/en/guides/integrations-guide/sitemap/#configuration). </details> <details> <summary>withastro/astro (astro)</summary> ### [`v5.13.2`](https://github.com/withastro/astro/blob/HEAD/packages/astro/CHANGELOG.md#5132) [Compare Source](https://github.com/withastro/astro/compare/astro@5.13.1...astro@5.13.2) ##### Patch Changes - [`4d16de7`](https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Improves the detection of remote paths in the `_image` endpoint. Now `href` parameters that start with `//` are considered remote paths. - Updated dependencies \[[`4d16de7`](https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820)]: - [@&#8203;astrojs/internal-helpers](https://github.com/astrojs/internal-helpers)@&#8203;0.7.2 - [@&#8203;astrojs/markdown-remark](https://github.com/astrojs/markdown-remark)@&#8203;6.3.6 ### [`v5.13.1`](https://github.com/withastro/astro/blob/HEAD/packages/astro/CHANGELOG.md#5131) [Compare Source](https://github.com/withastro/astro/compare/astro@5.13.0...astro@5.13.1) ##### Patch Changes - [#&#8203;14225](https://github.com/withastro/astro/pull/14225) [`f2490ab`](https://github.com/withastro/astro/commit/f2490aba420a8999c0e8d12b9e1e69d4e33ae29e) Thanks [@&#8203;delucis](https://github.com/delucis)! - Fixes the `experimental.chromeDevtoolsWorkspace` feature. ### [`v5.13.0`](https://github.com/withastro/astro/blob/HEAD/packages/astro/CHANGELOG.md#5130) [Compare Source](https://github.com/withastro/astro/compare/astro@5.12.9...astro@5.13.0) ##### Minor Changes - [#&#8203;14173](https://github.com/withastro/astro/pull/14173) [`39911b8`](https://github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038) Thanks [@&#8203;florian-lefebvre](https://github.com/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](https://docs.astro.build/en/guides/environment-variables/#type-safe-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](https://vite.dev/guide/env-and-mode.html#env-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: ```diff // 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: ```diff // 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: ```diff // 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: ```diff // 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](https://docs.astro.build/en/reference/experimental-flags/static-import-meta-env/) for more information about this feature. You can learn more about using environment variables in Astro, including `astro:env`, in the [environment variables documentation](https://docs.astro.build/en/guides/environment-variables/). - [#&#8203;14122](https://github.com/withastro/astro/pull/14122) [`41ed3ac`](https://github.com/withastro/astro/commit/41ed3ac54adf1025a38031757ee0bfaef8504092) Thanks [@&#8203;ascorbic](https://github.com/ascorbic)! - Adds experimental support for automatic [Chrome DevTools workspace folders](https://developer.chrome.com/docs/devtools/workspaces) 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: ```js // astro.config.mjs import { defineConfig } from 'astro/config'; export default defineConfig({ experimental: { chromeDevtoolsWorkspace: true, }, }); ``` See the [experimental Chrome DevTools workspace feature documentation](https://docs.astro.build/en/reference/experimental-flags/chrome-devtools-workspace/) for more information. </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. --- - [ ] <!-- rebase-check -->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-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xLjMiLCJ1cGRhdGVkSW5WZXIiOiI0MS4xLjMiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbImF1dG9tZXJnZSIsImRlcGVuZGVuY3kiXX0=-->
renovate-bot added the
automerge
dependency
 labels 2025-08-16 00:02:01 +00:00
renovate-bot added 1 commit 2025-08-16 00:02:01 +00:00
Update astro monorepo
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
test-build / build (pull_request) Successful in 54s
Details
1c9bd53861
renovate-bot force-pushed renovate/astro-monorepo from 1c9bd53861 to 8d1ca24a65 2025-08-16 00:03:59 +00:00 Compare
renovate-bot force-pushed renovate/astro-monorepo from 8d1ca24a65 to ede389e0c0 2025-08-17 00:01:34 +00:00 Compare
renovate-bot force-pushed renovate/astro-monorepo from ede389e0c0 to d04967e435 2025-08-17 00:02:42 +00:00 Compare
alexlebens merged commit d7b0b846d2 into main 2025-08-17 02:13:39 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Renovate
Issue generated by Renovate.
automerge
This PR will be automerged by Renovate.
dependency
Dependency update generated by Renovate.
stale
PR or Issue that has not been updated recently.
No Label
automerge
dependency
Milestone
No items
No Milestone
Assignees
Clear assignees
gitea-bot renovate-bot alexlebens
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alexlebens/site-profile#73
No description provided.
Delete Branch "renovate/astro-monorepo"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?