Bump the dev-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the dev-dependencies group with 3 updates in the /docs directory: @astrojs/starlight, astro and sass.

Updates @astrojs/starlight from 0.36.2 to 0.37.4

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.37.4

Patch Changes

• #3534 703fab0 Thanks @​HiDeoo! - Fixes support for running builds when npx is unavailable.

  Previously, Starlight would spawn a process to run the Pagefind search indexing binary using npx. On platforms where npx isn’t available, this could cause issues. Starlight now runs Pagefind using its Node.js API to avoid a separate process. As a side effect, you may notice that logging during builds is now less verbose.

• #3656 a0e6368 Thanks @​delucis! - Fixes several edge cases in highlighting the current page heading in Starlight’s table of contents

• #3663 00cbf00 Thanks @​lines-of-codes! - Adds Thai language support

• #3658 ac79329 Thanks @​delucis! - Avoids adding redundant aria-current="false" attributes to sidebar entries

• #3382 db295c2 Thanks @​trueberryless! - Fixes an issue where the mobile table of contents is unable to find the first heading when a page has a tall banner.

@​astrojs/starlight@​0.37.3

Patch Changes

• #3648 292666c Thanks @​maxchang3! - Prevents unwanted font size adjustments on iOS after orientation changes.

@​astrojs/starlight@​0.37.2

Patch Changes

• #3647 9f4efc3 Thanks @​gerstenbergit! - Adds Greek language support

@​astrojs/starlight@​0.37.1

Patch Changes

• #3603 30f6e7f Thanks @​delucis! - Fixes support for providing an absolute URL to Starlight’s favicon configuration option

@​astrojs/starlight@​0.37.0

Minor Changes

• #3491 28810f0 Thanks @​JusticeMatthew! - Changes text overflow styling in Markdown content

  ⚠️ Potentially breaking change: This release switches the overflow-wrap CSS style for common elements to break-word. In most cases, there should be little visual impact, but this change can impact how layouts with implicit sizing (such as tables) look, improving legibility in how words wrap.

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

  p, h1, h2, h3, h4, h5, h6, code {
    overflow-wrap: anywhere;
  }

• #3351 239698c Thanks @​HiDeoo! - Ensures that Starlight CSS layer order is predictable in custom pages using the <StarlightPage> component.

  Previously, due to how import order works in Astro, the <StarlightPage> component had to be the first import in custom pages to set up cascade layers used internally by Starlight to manage the order of its styles.

  With this change, this restriction no longer applies and Starlight’s styles will be applied correctly regardless of the import order of the <StarlightPage> component.

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.37.4

Patch Changes

• #3534 703fab0 Thanks @​HiDeoo! - Fixes support for running builds when npx is unavailable.

  Previously, Starlight would spawn a process to run the Pagefind search indexing binary using npx. On platforms where npx isn’t available, this could cause issues. Starlight now runs Pagefind using its Node.js API to avoid a separate process. As a side effect, you may notice that logging during builds is now less verbose.

• #3656 a0e6368 Thanks @​delucis! - Fixes several edge cases in highlighting the current page heading in Starlight’s table of contents

• #3663 00cbf00 Thanks @​lines-of-codes! - Adds Thai language support

• #3658 ac79329 Thanks @​delucis! - Avoids adding redundant aria-current="false" attributes to sidebar entries

• #3382 db295c2 Thanks @​trueberryless! - Fixes an issue where the mobile table of contents is unable to find the first heading when a page has a tall banner.

0.37.3

Patch Changes

• #3648 292666c Thanks @​maxchang3! - Prevents unwanted font size adjustments on iOS after orientation changes.

0.37.2

Patch Changes

• #3647 9f4efc3 Thanks @​gerstenbergit! - Adds Greek language support

0.37.1

Patch Changes

• #3603 30f6e7f Thanks @​delucis! - Fixes support for providing an absolute URL to Starlight’s favicon configuration option

0.37.0

Minor Changes

• #3491 28810f0 Thanks @​JusticeMatthew! - Changes text overflow styling in Markdown content

  ⚠️ Potentially breaking change: This release switches the overflow-wrap CSS style for common elements to break-word. In most cases, there should be little visual impact, but this change can impact how layouts with implicit sizing (such as tables) look, improving legibility in how words wrap.

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

  p,
  h1,
  h2,
  h3,
  h4,

... (truncated)

Commits

• 879d6b3 [ci] release (#3659)
• db295c2 fix: mobile toc issue with custom banners (#3382)
• a0e6368 Fix table of contents intersection observer (#3656)
• 703fab0 Pagefind CLI → Pagefind API (#3534)
• 42ff0aa [ci] format
• 00cbf00 i18n(th): Add Thai translations to Starlight UI (#3663)
• ac79329 Avoid adding redundant aria-current="false" to sidebar entries (#3658)
• bd54da3 [ci] release (#3654)
• 292666c Fix: Prevent font-size adjustments on iOS after orientation change (#3648)
• 5387d33 [ci] release (#3650)
• Additional commits viewable in compare view

Updates astro from 5.16.11 to 5.16.15

Release notes

Sourced from astro's releases.

astro@5.16.15

Patch Changes

• #15286 0aafc83 Thanks @​florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local provider

astro@5.16.14

Patch Changes

• #15213 c775fce Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Updates how the local provider must be used when using the experimental Fonts API

  Previously, there were 2 kinds of font providers: remote and local.

  Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:

  -import { defineConfig } from "astro/config";
  +import { defineConfig, fontProviders } from "astro/config";
  export default defineConfig({
  experimental: {
  fonts: [{
  name: "Custom",
  cssVariable: "--font-custom",
  
  
         provider: "local",
  
  
  
  
  
         provider: fontProviders.local(),
  
  
  
         options: {
        variants: [
            {
                weight: 400,
                style: "normal",
                src: ["./src/assets/fonts/custom-400.woff2"]
            },
            {
                weight: 700,
                style: "normal",
                src: ["./src/assets/fonts/custom-700.woff2"]
            }
            // ...
        ]
  
  
  
         }
    }]
  
  }
  });

Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.

See the experimental Fonts API docs for more information.

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.15

Patch Changes

• #15286 0aafc83 Thanks @​florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local provider

5.16.14

Patch Changes

• #15213 c775fce Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Updates how the local provider must be used when using the experimental Fonts API

  Previously, there were 2 kinds of font providers: remote and local.

  Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:

  -import { defineConfig } from "astro/config";
  +import { defineConfig, fontProviders } from "astro/config";
  export default defineConfig({
  experimental: {
  fonts: [{
  name: "Custom",
  cssVariable: "--font-custom",
  
  
         provider: "local",
  
  
  
  
  
         provider: fontProviders.local(),
  
  
  
         options: {
        variants: [
            {
                weight: 400,
                style: "normal",
                src: ["./src/assets/fonts/custom-400.woff2"]
            },
            {
                weight: 700,
                style: "normal",
                src: ["./src/assets/fonts/custom-700.woff2"]
            }
            // ...
        ]
  
  
  
         }
    }]
  
  }
  });

Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.

... (truncated)

Commits

• 8ca97e1 [ci] release (#15288)
• 0aafc83 fix(fonts): font providers as class instances (#15286)
• f7a8415 [ci] release (#15278)
• 7db2fda address sarah's feedback (#15280)
• c775fce feat(fonts)!: local provider unification (#15213)
• edabeaa fix(cli): add .vercel to .gitignore when using astro add vercel (#15185)
• ce0c346 [ci] release (#15270)
• 60d1045 clear fonts test cache (#15274)
• c4a15a8 [ci] format
• cb60ee1 feat(fonts): getFontBuffer() (#15182)
• Additional commits viewable in compare view

Updates sass from 1.93.3 to 1.97.3

Release notes

Sourced from sass's releases.

Dart Sass 1.97.3

To install Sass 1.97.3, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Fix a bug where nesting an at-rule within multiple style rules in plain CSS could cause outer style rules to be omitted.

See the full changelog for changes in earlier releases.

Dart Sass 1.97.2

To install Sass 1.97.2, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Additional fixes for implicit configuration when nested imports are involved.

See the full changelog for changes in earlier releases.

Dart Sass 1.97.1

To install Sass 1.97.1, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Fix a bug with the new CSS-style if() syntax where values would be evaluated even if their conditions didn't match.

See the full changelog for changes in earlier releases.

Dart Sass 1.97.0

To install Sass 1.97.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Add support for the display-p3-linear color space.

See the full changelog for changes in earlier releases.

Dart Sass 1.96.0

To install Sass 1.96.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

... (truncated)

Changelog

Sourced from sass's changelog.

1.97.3

• Fix a bug where nesting an at-rule within multiple style rules in plain CSS could cause outer style rules to be omitted.

1.97.2

• Additional fixes for implicit configuration when nested imports are involved.

1.97.1

• Fix a bug with the new CSS-style if() syntax where values would be evaluated even if their conditions didn't match.

1.97.0

• Add support for the display-p3-linear color space.

1.96.0

• Allow numbers with complex units (more than one numerator unit or more than zero denominator units) to be emitted to CSS. These are now emitted as calc() expressions, which now support complex units in plain CSS.

1.95.1

• No user-visible changes.

1.95.0

• Add support for the CSS-style if() function. In addition to supporting the plain CSS syntax, this also supports a sass() query that takes a Sass expression that evaluates to true or false at preprocessing time depending on whether the Sass value is truthy. If there are no plain-CSS queries, the function will return the first value whose query returns true during preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3) returns 2.

• The old Sass if() syntax is now deprecated. Users are encouraged to migrate to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to if(sass($condition): $if-true; else: $if-false).

  See the Sass website for details.

• Plain-CSS if() functions are now considered "special numbers", meaning that they can be used in place of arguments to CSS color functions.

• Plain-CSS if() functions and attr() functions are now considered "special

... (truncated)

Commits

• 080eaef Fix at-rules combined with plain CSS nesting (#2725)
• f6f73f8 Bump gts from 6.0.2 to 7.0.0 in /pkg/sass-parser (#2711)
• 0b87dd7 Bump protobuf and protoc_plugin (#2723)
• d12cc7d Fix bug with implicit configuration for nested imports (#2658)
• 340bfd2 Bump actions/download-artifact from 6 to 7 (#2706)
• a795ab3 Bump actions/upload-artifact from 5 to 6 (#2705)
• add7e6f Bump protoc_plugin from 23.0.0 to 24.0.0 (#2696)
• 62ec662 Use pwsh instead of powershell (#2710)
• b2f2532 Don't evaluate if() values if the condition doesn't match (#2707)
• 0c7083a Add support for the display-p3-linear color space (#2703)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for sass 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 <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

[github-actions]

Package	Line Rate	Branch Rate	Complexity	Health
StageZero.Playwright	76%	60%	72	✔
StageZero	100%	100%	5	✔
StageZero.Selenium	63%	38%	103	➖
Summary	68% (483 / 709)	45% (35 / 78)	180	➖