Skip to content

build(deps): bump the starlight_astro group in /docs with 4 updates #103

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 Jul 21, 2025

Bumps the starlight_astro group in /docs with 4 updates: @astrojs/starlight, astro, @astrojs/markdown-remark and @astrojs/mdx.

Updates @astrojs/starlight from 0.34.5 to 0.35.1

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.35.1

Patch Changes

@​astrojs/starlight@​0.35.0

Minor Changes

  • #2261 778b743 Thanks @​shubham-padia! - Adds support for using any of Starlight’s built-in icons in asides.

  • #3272 e7fe267 Thanks @​delucis! - Adds a new generateId option to Starlight’s docsLoader()

    This enables overriding the default sluggifier used to convert content filenames to URLs.

  • #3276 3917b20 Thanks @​delucis! - Excludes banner content from search results

    Previously, content set in banner in page frontmatter was indexed by Starlight’s default search provider Pagefind. This could cause unexpected search results, especially for sites setting a common banner content on multiple pages. Starlight’s default Banner component is now excluded from search indexing.

    This change does not impact Banner overrides using custom components.

  • #3266 1161af0 Thanks @​HiDeoo! - Adds support for custom HTML attributes on autogenerated sidebar links using the autogenerate.attrs option.

  • #3274 80ccff7 Thanks @​HiDeoo! - Fixes an issue where some Starlight remark and rehype plugins were transforming Markdown and MDX content in non-Starlight pages.

    ⚠️ BREAKING CHANGE:

    Previously, some of Starlight’s remark and rehype plugins, most notably the plugin transforming Starlight's custom Markdown syntax for rendering asides, were applied to all Markdown and MDX content. This included content from individual Markdown pages and content from content collections other than the docs collection used by Starlight.

    This change restricts the application of Starlight’s remark and rehype plugins to only Markdown and MDX content loaded using Starlight's docsLoader(). If you were relying on this behavior, please let us know about your use case in the dedicated #starlight channel in the Astro Discord or by opening an issue.

Patch Changes

  • #3266 1161af0 Thanks @​HiDeoo! - Ensures invalid sidebar group configurations using the attrs option are properly reported as a type error.

    Previously, invalid sidebar group configurations using the attrs option were not reported as a type error but only surfaced at runtime. This change is only a type-level change and does not affect the runtime behavior of Starlight which does not support the attrs option for sidebar groups.

  • #3274 80ccff7 Thanks @​HiDeoo! - Prevents Starlight remark and rehype plugins from transforming Markdown and MDX content when using the Astro renderMarkdown() content loader API.

@​astrojs/starlight@​0.34.8

Patch Changes

  • #3306 21fcd94 Thanks @​HiDeoo! - Fixes a regression in Starlight version 0.34.5 that caused multilingual sites with a default locale explicitly set to root to report a configuration error.

@​astrojs/starlight@​0.34.7

Patch Changes

@​astrojs/starlight@​0.34.6

Patch Changes

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.35.1

Patch Changes

0.35.0

Minor Changes

  • #2261 778b743 Thanks @​shubham-padia! - Adds support for using any of Starlight’s built-in icons in asides.

  • #3272 e7fe267 Thanks @​delucis! - Adds a new generateId option to Starlight’s docsLoader()

    This enables overriding the default sluggifier used to convert content filenames to URLs.

  • #3276 3917b20 Thanks @​delucis! - Excludes banner content from search results

    Previously, content set in banner in page frontmatter was indexed by Starlight’s default search provider Pagefind. This could cause unexpected search results, especially for sites setting a common banner content on multiple pages. Starlight’s default Banner component is now excluded from search indexing.

    This change does not impact Banner overrides using custom components.

  • #3266 1161af0 Thanks @​HiDeoo! - Adds support for custom HTML attributes on autogenerated sidebar links using the autogenerate.attrs option.

  • #3274 80ccff7 Thanks @​HiDeoo! - Fixes an issue where some Starlight remark and rehype plugins were transforming Markdown and MDX content in non-Starlight pages.

    ⚠️ BREAKING CHANGE:

    Previously, some of Starlight’s remark and rehype plugins, most notably the plugin transforming Starlight's custom Markdown syntax for rendering asides, were applied to all Markdown and MDX content. This included content from individual Markdown pages and content from content collections other than the docs collection used by Starlight.

    This change restricts the application of Starlight’s remark and rehype plugins to only Markdown and MDX content loaded using Starlight's docsLoader(). If you were relying on this behavior, please let us know about your use case in the dedicated #starlight channel in the Astro Discord or by opening an issue.

Patch Changes

  • #3266 1161af0 Thanks @​HiDeoo! - Ensures invalid sidebar group configurations using the attrs option are properly reported as a type error.

    Previously, invalid sidebar group configurations using the attrs option were not reported as a type error but only surfaced at runtime. This change is only a type-level change and does not affect the runtime behavior of Starlight which does not support the attrs option for sidebar groups.

  • #3274 80ccff7 Thanks @​HiDeoo! - Prevents Starlight remark and rehype plugins from transforming Markdown and MDX content when using the Astro renderMarkdown() content loader API.

0.34.8

Patch Changes

  • #3306 21fcd94 Thanks @​HiDeoo! - Fixes a regression in Starlight version 0.34.5 that caused multilingual sites with a default locale explicitly set to root to report a configuration error.

0.34.7

Patch Changes

... (truncated)

Commits

Updates astro from 5.11.0 to 5.12.0

Release notes

Sourced from astro's releases.

[email protected]

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: /* ... */
    })
  • ... (truncated)

    Changelog

    Sourced from astro's changelog.

    5.12.0

    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: /* ... */
  • ... (truncated)

    Commits

    Updates @astrojs/markdown-remark from 6.3.2 to 6.3.3

    Release notes

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

    @​astrojs/markdown-remark@​6.3.3

    Patch Changes

    • #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.

    Changelog

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

    6.3.3

    Patch Changes

    • #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.

    Commits

    Updates @astrojs/mdx from 4.3.0 to 4.3.1

    Release notes

    Sourced from @​astrojs/mdx's releases.

    @​astrojs/mdx@​4.3.1

    Patch Changes

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

    Sourced from @​astrojs/mdx's changelog.

    4.3.1

    Patch Changes

    • Updated dependencies [6bd5f75]:
      • @​astrojs/markdown-remark@​6.3.3
    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 4 updates: [@astrojs/starlight](https://github.com/withastro/starlight/tree/HEAD/packages/starlight), [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro), [@astrojs/markdown-remark](https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark) and [@astrojs/mdx](https://github.com/withastro/astro/tree/HEAD/packages/integrations/mdx).
    
    
    Updates `@astrojs/starlight` from 0.34.5 to 0.35.1
    - [Release notes](https://github.com/withastro/starlight/releases)
    - [Changelog](https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md)
    - [Commits](https://github.com/withastro/starlight/commits/@astrojs/[email protected]/packages/starlight)
    
    Updates `astro` from 5.11.0 to 5.12.0
    - [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/[email protected]/packages/astro)
    
    Updates `@astrojs/markdown-remark` from 6.3.2 to 6.3.3
    - [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/[email protected]/packages/markdown/remark)
    
    Updates `@astrojs/mdx` from 4.3.0 to 4.3.1
    - [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/[email protected]/packages/integrations/mdx)
    
    ---
    updated-dependencies:
    - dependency-name: "@astrojs/starlight"
      dependency-version: 0.35.1
      dependency-type: direct:production
      update-type: version-update:semver-minor
      dependency-group: starlight_astro
    - dependency-name: astro
      dependency-version: 5.12.0
      dependency-type: direct:production
      update-type: version-update:semver-minor
      dependency-group: starlight_astro
    - dependency-name: "@astrojs/markdown-remark"
      dependency-version: 6.3.3
      dependency-type: direct:development
      update-type: version-update:semver-patch
      dependency-group: starlight_astro
    - dependency-name: "@astrojs/mdx"
      dependency-version: 4.3.1
      dependency-type: direct:development
      update-type: version-update:semver-patch
      dependency-group: starlight_astro
    ...
    
    Signed-off-by: dependabot[bot] <[email protected]>
    @dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 21, 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