Bump astro and @astrojs/starlight in /starlight

[dependabot]

Bumps astro and @astrojs/starlight. These dependencies needed to be updated together.
Updates astro from 3.0.8 to 5.13.2

Release notes

Sourced from astro's releases.

[email protected]

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

[email protected]

Patch Changes

• #14225 f2490ab Thanks @​delucis! - Fixes the experimental.chromeDevtoolsWorkspace feature.

[email protected]

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.

3.6.4

Patch Changes

• #9226 8f8a40e93 Thanks @​outofambit! - Fix i18n fallback routing with routing strategy of always-prefix

• #9179 3f28336d9 Thanks @​lilnasy! - Fixes an issue where the presence of a slot in a page led to an error.

• #9219 067a65f5b Thanks @​natemoo-re! - Fix edge case where <style> updates inside of .astro files would occasionally fail to update without reloading the page.

• #9236 27d3e86e4 Thanks @​ematipico! - The configuration i18n.routingStrategy has been replaced with an object called routing.

  export default defineConfig({
    experimental: {
        i18n: {
  -          routingStrategy: "prefix-always",
  +          routing: {
  +              prefixDefaultLocale: true,
  +          }
        }
    }
  })

  export default defineConfig({
    experimental: {
        i18n: {
  -          routingStrategy: "prefix-other-locales",
  +          routing: {
  +              prefixDefaultLocale: false,
  +          }
        }
    }
  })

3.6.3

Patch Changes

• #9193 0dc99c9a2 Thanks @​florian-lefebvre! - Prevents the Code component from crashing if the lang isn't supported by falling back to plaintext.

3.6.2

Patch Changes

• #9189 d90714fc3 Thanks @​SpencerWhitehead7! - Fixes an issue where links with the same pathname as the current page, but different search params, were not prefetched.

... (truncated)

Commits

• 9288133 [ci] release (#14232)
• 1040510 [ci] format
• 4d16de7 Merge commit from fork
• 1591bc7 [ci] release (#14227)
• f2490ab Fix automatic Chrome DevTools workspace feature (#14225)
• a186848 [ci] release (#14217)
• b33780d [ci] format
• 39911b8 feat: experimental static import.meta.env (#14173)
• 41ed3ac feat: add automatic chrome workspace handling (#14122)
• 806d2dc chore: add additional contributor to changelog (#14203)
• Additional commits viewable in compare view

Updates @astrojs/starlight from 0.9.0 to 0.35.2

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.35.2

Patch Changes

• #3341 10f6fe2 Thanks @​HiDeoo! - Prevents potential build issues with the Astro Cloudflare adapter due to the dependency on Node.js builtins.

• #3327 bf58c60 Thanks @​delucis! - Fixes a routing bug for docs pages with a slug authored with non-normalized composition. This could occur for filenames containing diacritics in some circumstances, causing 404s.

@​astrojs/starlight@​0.35.1

Patch Changes

• #3325 4cf28f2 Thanks @​mniinio! - Adds Finnish language support

@​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.

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.35.2

Patch Changes

• #3341 10f6fe2 Thanks @​HiDeoo! - Prevents potential build issues with the Astro Cloudflare adapter due to the dependency on Node.js builtins.

• #3327 bf58c60 Thanks @​delucis! - Fixes a routing bug for docs pages with a slug authored with non-normalized composition. This could occur for filenames containing diacritics in some circumstances, causing 404s.

0.35.1

Patch Changes

• #3325 4cf28f2 Thanks @​mniinio! - Adds Finnish language support

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

... (truncated)

Commits

• cfd5185 [ci] release (#3328)
• 10f6fe2 Prevent Cloudflare build issues due to Node.js builtins usage (#3341)
• bf58c60 Fix a routing issue with unnormalized content collection slugs (#3327)
• bec2c47 [ci] release (#3326)
• 4cf28f2 Support for Finnish language (fi) (#3325)
• 7447fe5 [ci] release (#3308)
• e7fe267 Support passing generateId to docsLoader() (#3272)
• 1161af0 Autogenerated link custom attributes (#3266)
• 778b743 Aside: Support custom icons (#2261)
• 3917b20 Exclude banner content from Pagefind indexing (#3276)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by matthewp, a new releaser for @​astrojs/starlight since your current version.

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dependabot]

Superseded by #423.