Skip to content

build(deps): bump the starlight_astro group in /docs with 5 updates #119

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 18, 2025

Bumps the starlight_astro group in /docs with 5 updates:

Package From To
astro 5.12.8 5.13.2
starlight-links-validator 0.17.0 0.17.1
@astrojs/sitemap 3.4.2 3.5.0
@astrojs/markdown-remark 6.3.5 6.3.6
@astrojs/mdx 4.3.3 4.3.4

Updates astro from 5.12.8 to 5.13.2

Release notes

Sourced from astro's releases.

astro@5.13.2

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

astro@5.13.1

Patch Changes

astro@5.13.0

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;

... (truncated)

Changelog

Sourced from astro's changelog.

5.13.2

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

5.13.1

Patch Changes

5.13.0

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:

... (truncated)

Commits

Updates starlight-links-validator from 0.17.0 to 0.17.1

Release notes

Sourced from starlight-links-validator's releases.

starlight-links-validator@0.17.1

Patch Changes

Changelog

Sourced from starlight-links-validator's changelog.

0.17.1

Patch Changes

Commits

Updates @astrojs/sitemap from 3.4.2 to 3.5.0

Release notes

Sourced from @​astrojs/sitemap's releases.

@​astrojs/sitemap@​3.5.0

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.

Changelog

Sourced from @​astrojs/sitemap's changelog.

3.5.0

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.

Commits

Updates @astrojs/markdown-remark from 6.3.5 to 6.3.6

Release notes

Sourced from @​astrojs/markdown-remark's releases.

@​astrojs/markdown-remark@​6.3.6

Patch Changes

  • Updated dependencies [4d16de7]:
    • @​astrojs/internal-helpers@​0.7.2
Changelog

Sourced from @​astrojs/markdown-remark's changelog.

6.3.6

Patch Changes

  • Updated dependencies [4d16de7]:
    • @​astrojs/internal-helpers@​0.7.2
Commits

Updates @astrojs/mdx from 4.3.3 to 4.3.4

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​4.3.4

Patch Changes

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

Sourced from @​astrojs/mdx's changelog.

4.3.4

Patch Changes

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

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

Bumps the starlight_astro group in /docs with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) | `5.12.8` | `5.13.2` |
| [starlight-links-validator](https://github.com/HiDeoo/starlight-links-validator/tree/HEAD/packages/starlight-links-validator) | `0.17.0` | `0.17.1` |
| [@astrojs/sitemap](https://github.com/withastro/astro/tree/HEAD/packages/integrations/sitemap) | `3.4.2` | `3.5.0` |
| [@astrojs/markdown-remark](https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark) | `6.3.5` | `6.3.6` |
| [@astrojs/mdx](https://github.com/withastro/astro/tree/HEAD/packages/integrations/mdx) | `4.3.3` | `4.3.4` |


Updates `astro` from 5.12.8 to 5.13.2
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/astro@5.13.2/packages/astro)

Updates `starlight-links-validator` from 0.17.0 to 0.17.1
- [Release notes](https://github.com/HiDeoo/starlight-links-validator/releases)
- [Changelog](https://github.com/HiDeoo/starlight-links-validator/blob/main/packages/starlight-links-validator/CHANGELOG.md)
- [Commits](https://github.com/HiDeoo/starlight-links-validator/commits/starlight-links-validator@0.17.1/packages/starlight-links-validator)

Updates `@astrojs/sitemap` from 3.4.2 to 3.5.0
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/sitemap/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/sitemap@3.5.0/packages/integrations/sitemap)

Updates `@astrojs/markdown-remark` from 6.3.5 to 6.3.6
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/markdown/remark/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/markdown-remark@6.3.6/packages/markdown/remark)

Updates `@astrojs/mdx` from 4.3.3 to 4.3.4
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/mdx/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/mdx@4.3.4/packages/integrations/mdx)

---
updated-dependencies:
- dependency-name: astro
  dependency-version: 5.13.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: starlight_astro
- dependency-name: starlight-links-validator
  dependency-version: 0.17.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: starlight_astro
- dependency-name: "@astrojs/sitemap"
  dependency-version: 3.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: starlight_astro
- dependency-name: "@astrojs/markdown-remark"
  dependency-version: 6.3.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: starlight_astro
- dependency-name: "@astrojs/mdx"
  dependency-version: 4.3.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: starlight_astro
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants