bump(deps): bump astro and @astrojs/starlight in /web

[dependabot]

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

Release notes

Sourced from astro's releases.

astro@5.14.4

Patch Changes

• #14509 7e04caf Thanks @​ArmandPhilippot! - Fixes an error in the docs that specified an incorrect version for the security.allowedDomains release.

astro@5.14.3

Patch Changes

• #14505 28b2a1d Thanks @​matthewp! - Fixes Cannot set property manifest error in test utilities by adding a protected setter for the manifest property

• #14235 c4d84bb Thanks @​toxeeec! - Fixes a bug where the "tap" prefetch strategy worked only on the first clicked link with view transitions enabled

astro@5.14.1

Patch Changes

• #14440 a3e16ab Thanks @​florian-lefebvre! - Fixes a case where the URLs generated by the experimental Fonts API would be incorrect in dev

astro@5.14.0

Minor Changes

• #13520 a31edb8 Thanks @​openscript! - Adds a new property routePattern available to GetStaticPathsOptions

  This provides the original, dynamic segment definition in a routing file path (e.g. /[...locale]/[files]/[slug]) from the Astro render context that would not otherwise be available within the scope of getStaticPaths(). This can be useful to calculate the params and props for each page route.

  For example, you can now localize your route segments and return an array of static paths by passing routePattern to a custom getLocalizedData() helper function. The params object will be set with explicit values for each route segment (e.g. locale, files, and slug). Then, these values will be used to generate the routes and can be used in your page template via Astro.params.

  // src/pages/[...locale]/[files]/[slug].astro
  import { getLocalizedData } from "../../../utils/i18n"; export async function getStaticPaths({ routePattern
  }) { const response = await fetch('...'); const data = await response.json(); console.log(routePattern);
  // [...locale]/[files]/[slug] // Call your custom helper with routePattern to generate the static
  paths return data.flatMap((file) => getLocalizedData(file, routePattern)); } const { locale, files,
  slug } = Astro.params;

  For more information about this advanced routing pattern, see Astro's routing reference.

• #13651 dcfbd8c Thanks @​ADTC! - Adds a new SvgComponent type

  You can now more easily enforce type safety for your .svg assets by directly importing SVGComponent from astro/types:

  ---
  // src/components/Logo.astro
  import type { SvgComponent } from 'astro/types';
  import HomeIcon from './Home.svg';
  interface Link {
    url: string;
    text: string;

... (truncated)

Changelog

Sourced from astro's changelog.

5.14.4

Patch Changes

• #14509 7e04caf Thanks @​ArmandPhilippot! - Fixes an error in the docs that specified an incorrect version for the security.allowedDomains release.

5.14.3

Patch Changes

• #14505 28b2a1d Thanks @​matthewp! - Fixes Cannot set property manifest error in test utilities by adding a protected setter for the manifest property

• #14235 c4d84bb Thanks @​toxeeec! - Fixes a bug where the "tap" prefetch strategy worked only on the first clicked link with view transitions enabled

5.14.2

Patch Changes

• #14459 916f9c2 Thanks @​florian-lefebvre! - Improves font files URLs in development when using the experimental fonts API by showing the subset if present

• b8ca69b Thanks @​ascorbic! - Aligns dev image server file base with Vite rules

• #14469 1c090b0 Thanks @​delucis! - Updates tinyexec dependency

• #14460 008dc75 Thanks @​florian-lefebvre! - Fixes a case where astro:config/server values typed as URLs would be serialized as strings

• #13730 7260367 Thanks @​razonyang! - Fixes a bug in i18n, where Astro caused an infinite loop when a locale that doesn't have an index, and Astro falls back to the index of the default locale.

• 6ee63bf Thanks @​matthewp! - Adds security.allowedDomains configuration to validate X-Forwarded-Host headers in SSR

  The X-Forwarded-Host header will now only be trusted if it matches one of the configured allowed host patterns. This prevents host header injection attacks that can lead to cache poisoning and other security vulnerabilities.

  Configure allowed host patterns to enable X-Forwarded-Host support:

  // astro.config.mjs
  export default defineConfig({
    output: 'server',
    adapter: node(),
    security: {
      allowedDomains: [
        { hostname: 'example.com' },
        { hostname: '*.example.com' },
        { hostname: 'cdn.example.com', port: '443' },
      ],
    },
  });

  The patterns support wildcards (* and **) for flexible hostname matching and can optionally specify protocol and port.

... (truncated)

Commits

• 3412859 [ci] release (#14510)
• 7e04caf docs: fix security.allowedDomains version (#14509)
• fe1d35c [ci] release (#14507)
• 7926882 [ci] format
• c4d84bb fix(prefetch): Fix "tap" prefetch strategy when view transitions are enabled ...
• 3bb14b7 [ci] release (#14466)
• 7a5aaff [ci] format
• 28b2a1d Fix failing x-forwarded-host tests (#14505)
• ec307b0 [ci] format
• 6ee63bf Merge commit from fork
• Additional commits viewable in compare view

Updates @astrojs/starlight from 0.25.2 to 0.36.0

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.36.0

Minor Changes

• #3427 c3b2d0f Thanks @​delucis! - Fixes styling of labels that wrap across multiple lines in <Tabs> component

  ⚠️ Potentially breaking change: Tab labels now have a narrower line-height and additional vertical padding. If you have custom CSS targetting the <Tabs> component, you may want to double check the visual appearance of your tabs when updating.

  If you want to preserve the previous styling, you can add the following custom CSS to your site:

  .tab > [role='tab'] {
    line-height: var(--sl-line-height);
    padding-block: 0;
  }

• #3380 3364af3 Thanks @​HiDeoo! - Makes head entry parsing stricter in Starlight config and content frontmatter.

  ⚠️ Potentially breaking change: Previously Starlight would accept a head entry for a meta tag defining some content which generates invalid HTML as <meta> is a void element which cannot have any child nodes. Now, it is an error to define a meta tag including some content.

  If you see errors after updating, look for head entries in the Starlight configuration in the astro.config.mjs file or in the frontmatter of your content files that include a content property for a meta tag. To fix the error, move the content property to the attrs object with at least an additional attribute to identify the kind of metadata it represents:

  head: {
    tag: 'meta',
  - content: 'foo',
    attrs: {
      name: 'my-meta',
  +   content: 'foo',
    },
  },

• #3340 2018c31 Thanks @​HiDeoo! - Adds missing vertical spacing between Markdown content and UI Framework components using client directives.

  ⚠️ Potentially breaking change: By default, Starlight applies some vertical spacing (--sl-content-gap-y) between Markdown content blocks. This change introduces similar spacing between Markdown content blocks and UI Framework components using client directives which was not present before.

  If you were relying on the previous behavior, you can manually override the spacing by manually specifying the top margin on the component using custom CSS, e.g. by relying on a CSS class to target the component.

  .my-custom-component {
    margin-top: 0;
  }

Patch Changes

• #3423 a0d0670 Thanks @​andersk! - Fixes HTML validity in sidebar groups by ensuring <summary> is the first child of <details>

@​astrojs/starlight@​0.35.3

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.36.0

Minor Changes

• #3427 c3b2d0f Thanks @​delucis! - Fixes styling of labels that wrap across multiple lines in <Tabs> component

  ⚠️ Potentially breaking change: Tab labels now have a narrower line-height and additional vertical padding. If you have custom CSS targetting the <Tabs> component, you may want to double check the visual appearance of your tabs when updating.

  If you want to preserve the previous styling, you can add the following custom CSS to your site:

  .tab > [role='tab'] {
    line-height: var(--sl-line-height);
    padding-block: 0;
  }

• #3380 3364af3 Thanks @​HiDeoo! - Makes head entry parsing stricter in Starlight config and content frontmatter.

  ⚠️ Potentially breaking change: Previously Starlight would accept a head entry for a meta tag defining some content which generates invalid HTML as <meta> is a void element which cannot have any child nodes. Now, it is an error to define a meta tag including some content.

  If you see errors after updating, look for head entries in the Starlight configuration in the astro.config.mjs file or in the frontmatter of your content files that include a content property for a meta tag. To fix the error, move the content property to the attrs object with at least an additional attribute to identify the kind of metadata it represents:

  head: {
    tag: 'meta',
  - content: 'foo',
    attrs: {
      name: 'my-meta',
  +   content: 'foo',
    },
  },

• #3340 2018c31 Thanks @​HiDeoo! - Adds missing vertical spacing between Markdown content and UI Framework components using client directives.

  ⚠️ Potentially breaking change: By default, Starlight applies some vertical spacing (--sl-content-gap-y) between Markdown content blocks. This change introduces similar spacing between Markdown content blocks and UI Framework components using client directives which was not present before.

  If you were relying on the previous behavior, you can manually override the spacing by manually specifying the top margin on the component using custom CSS, e.g. by relying on a CSS class to target the component.

  .my-custom-component {
    margin-top: 0;
  }

Patch Changes

• #3423 a0d0670 Thanks @​andersk! - Fixes HTML validity in sidebar groups by ensuring <summary> is the first child of <details>

... (truncated)

Commits

• eb8ac77 [ci] release (#3434)
• 3364af3 Add head config validation for meta tags with content (#3380)
• 2018c31 Fix Astro Island margins in Markdown (#3340)
• c3b2d0f Ensure tab links span the full tab height (#3427)
• a0d0670 Move \<summary> to top of \<details> for validity (#3423)
• 266eed4 [ci] release (#3384)
• fcc0633 i18n(de): Update page.lastUpdated translation to be more in‐line with the E...
• 97e8103 Remove invalid value attribute from \<select> (#3421)
• 9200fac Convert invalid \<div> child of \<summary> to \<span> (#3422)
• d1b3828 Add basic ESLint config, lint script and lint CI job (#1640)
• 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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}