chore(deps): bump the deps group across 1 directory with 2 updates

[dependabot]

Bumps the deps group with 2 updates in the /astro-starlight directory: @astrojs/starlight and astro.

Updates @astrojs/starlight from 0.27.1 to 0.32.2

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.32.2

Patch Changes

• #2926 c0170fd Thanks @​resoltico! - Adds Latvian language support

• #2918 790c000 Thanks @​HiDeoo! - Fixes a trailing slash inconsistency in generated sidebar links when using the trailingSlash: 'ignore' Astro option (the default) between internal and auto-generated links. Starlight behavior for this configuration value is to use a trailing slash as many common hosting providers redirect to URLs with a trailing slash by default.

@​astrojs/starlight@​0.32.1

Patch Changes

• #2904 ec5ca59 Thanks @​HiDeoo! - Fixes an issue preventing the use of rewrites.

@​astrojs/starlight@​0.32.0

Minor Changes

• #2390 f493361 Thanks @​delucis! - Moves route data to Astro.locals instead of passing it down via component props

  ⚠️ Breaking change: Previously, all of Starlight’s templating components, including user or plugin overrides, had access to a data object for the current route via Astro.props. This data is now available as Astro.locals.starlightRoute instead.

  To update, refactor any component overrides you have:

  • Remove imports of @astrojs/starlight/props, which is now deprecated.
  • Update code that accesses Astro.props to use Astro.locals.starlightRoute instead.
  • Remove any spreading of {...Astro.props} into child components, which is no longer required.

  In the following example, a custom override for Starlight’s LastUpdated component is updated for the new style:

  ---
  import Default from '@astrojs/starlight/components/LastUpdated.astro';
  - import type { Props } from '@astrojs/starlight/props';
  
  const { lastUpdated } = Astro.props;
  
  
  const { lastUpdated } = Astro.locals.starlightRoute;
  
  const updatedThisYear = lastUpdated?.getFullYear() === new Date().getFullYear();
  {updatedThisYear && (
  
  <Default {...Astro.props}><slot /></Default>
  
  
  <Default><slot /></Default>
  )}

Community Starlight plugins may also need to be manually updated to work with Starlight 0.32. If you encounter any issues, please reach out to the plugin author to see if it is a known issue or if an updated version is being worked on.

#2578 f895f75 Thanks @​HiDeoo! - Deprecates the Starlight plugin setup hook in favor of the new config:setup hook which provides the same functionality.

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.32.2

Patch Changes

• #2926 c0170fd Thanks @​resoltico! - Adds Latvian language support

• #2918 790c000 Thanks @​HiDeoo! - Fixes a trailing slash inconsistency in generated sidebar links when using the trailingSlash: 'ignore' Astro option (the default) between internal and auto-generated links. Starlight behavior for this configuration value is to use a trailing slash as many common hosting providers redirect to URLs with a trailing slash by default.

0.32.1

Patch Changes

• #2904 ec5ca59 Thanks @​HiDeoo! - Fixes an issue preventing the use of rewrites.

0.32.0

Minor Changes

• #2390 f493361 Thanks @​delucis! - Moves route data to Astro.locals instead of passing it down via component props

  ⚠️ Breaking change: Previously, all of Starlight’s templating components, including user or plugin overrides, had access to a data object for the current route via Astro.props. This data is now available as Astro.locals.starlightRoute instead.

  To update, refactor any component overrides you have:

  • Remove imports of @astrojs/starlight/props, which is now deprecated.
  • Update code that accesses Astro.props to use Astro.locals.starlightRoute instead.
  • Remove any spreading of {...Astro.props} into child components, which is no longer required.

  In the following example, a custom override for Starlight’s LastUpdated component is updated for the new style:

  ---
  import Default from '@astrojs/starlight/components/LastUpdated.astro';
  - import type { Props } from '@astrojs/starlight/props';
  
  const { lastUpdated } = Astro.props;
  
  
  const { lastUpdated } = Astro.locals.starlightRoute;
  
  const updatedThisYear = lastUpdated?.getFullYear() === new Date().getFullYear();
  {updatedThisYear && (
  
  <Default {...Astro.props}><slot /></Default>
  
  
  <Default><slot /></Default>
  )}

Community Starlight plugins may also need to be manually updated to work with Starlight 0.32. If you encounter any issues, please reach out to the plugin author to see if it is a known issue or if an updated version is being worked on.

... (truncated)

Commits

• 9a5450d [ci] release (#2920)
• c0170fd i18n: add lv.json (#2926)
• 790c000 Fix trailing slash inconsistency in sidebar links (#2918)
• 5a7e831 [ci] release (#2906)
• ec5ca59 Fix issue with rewriting (#2904)
• 9b32c6a [ci] release (#2861)
• f493361 Move route data to Astro.locals (#2390)
• f895f75 Expose FS translation system to plugins (#2578)
• 2df9d05 Support multisite search on pagefind (#2858)
• 9b32ba9 Fix some Pagefind UI issues (#2848)
• Additional commits viewable in compare view

Updates astro from 4.15.7 to 5.4.0

Release notes

Sourced from astro's releases.

[email protected]

Minor Changes

• #12052 5be12b2 Thanks @​Fryuni! - Exposes extra APIs for scripting and testing.

  Config helpers

  Two new helper functions exported from astro/config:

  • mergeConfig() allows users to merge partially defined Astro configurations on top of a base config while following the merge rules of updateConfig() available for integrations.
  • validateConfig() allows users to validate that a given value is a valid Astro configuration and fills in default values as necessary.

  These helpers are particularly useful for integration authors and for developers writing scripts that need to manipulate Astro configurations programmatically.

  Programmatic build

  The build API now receives a second optional BuildOptions argument where users can specify:

  • devOutput (default false): output a development-based build similar to code transformed in astro dev.
  • teardownCompiler (default true): teardown the compiler WASM instance after build.

  These options provide more control when running Astro builds programmatically, especially for testing scenarios or custom build pipelines.

• #13278 4a43c4b Thanks @​ematipico! - Adds a new configuration option server.allowedHosts and CLI option --allowed-hosts.

  Now you can specify the hostnames that the dev and preview servers are allowed to respond to. This is useful for allowing additional subdomains, or running the dev server in a web container.

  allowedHosts checks the Host header on HTTP requests from browsers and if it doesn't match, it will reject the request to prevent CSRF and XSS attacks.

  astro dev --allowed-hosts=foo.bar.example.com,bar.example.com

  astro preview --allowed-hosts=foo.bar.example.com,bar.example.com

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  export default defineConfig({
  server: {
  allowedHosts: ['foo.bar.example.com', 'bar.example.com'],
  },
  });

  This feature is the same as Vite's server.allowHosts configuration.

... (truncated)

Changelog

Sourced from astro's changelog.

5.4.0

Minor Changes

• #12052 5be12b2 Thanks @​Fryuni! - Exposes extra APIs for scripting and testing.

  Config helpers

  Two new helper functions exported from astro/config:

  • mergeConfig() allows users to merge partially defined Astro configurations on top of a base config while following the merge rules of updateConfig() available for integrations.
  • validateConfig() allows users to validate that a given value is a valid Astro configuration and fills in default values as necessary.

  These helpers are particularly useful for integration authors and for developers writing scripts that need to manipulate Astro configurations programmatically.

  Programmatic build

  The build API now receives a second optional BuildOptions argument where users can specify:

  • devOutput (default false): output a development-based build similar to code transformed in astro dev.
  • teardownCompiler (default true): teardown the compiler WASM instance after build.

  These options provide more control when running Astro builds programmatically, especially for testing scenarios or custom build pipelines.

• #13278 4a43c4b Thanks @​ematipico! - Adds a new configuration option server.allowedHosts and CLI option --allowed-hosts.

  Now you can specify the hostnames that the dev and preview servers are allowed to respond to. This is useful for allowing additional subdomains, or running the dev server in a web container.

  allowedHosts checks the Host header on HTTP requests from browsers and if it doesn't match, it will reject the request to prevent CSRF and XSS attacks.

  astro dev --allowed-hosts=foo.bar.example.com,bar.example.com

  astro preview --allowed-hosts=foo.bar.example.com,bar.example.com

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  export default defineConfig({
  server: {
  allowedHosts: ['foo.bar.example.com', 'bar.example.com'],
  },
  });

  This feature is the same as Vite's server.allowHosts configuration.

... (truncated)

Commits

• 9aa5ac1 [ci] release (#13318)
• 80926fa chore(deps): update esbuild and vite versions (#13323)
• 5b6df02 [ci] format
• 5f72a58 fix(core): double encoding during match of routes (#13303)
• 2154ada [ci] format
• 5be12b2 feat(astro): Exposes extra APIs for script and testing (#12052)
• eb47231 [ci] format
• 9e7c71d fixes property shadowing for form.attributes (#13313)
• 2cdeaea [ci] format
• 4a43c4b feat: add new allowedHosts option (#13278)
• Additional commits viewable in compare view

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

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[dependabot]

Superseded by #4614.