chore(deps): bump the dependencies group in /website with 3 updates

[dependabot]

Bumps the dependencies group in /website with 3 updates: @astrojs/starlight, astro and sharp.

Updates @astrojs/starlight from 0.35.3 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>

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>

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)
• See full diff in compare view

Updates astro from 5.13.7 to 5.14.1

Release notes

Sourced from astro's releases.

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;
    icon: SvgComponent;
  }
  const links: Link[] = [
    {
      url: '/',
      text: 'Home',
      icon: HomeIcon,
    },
  ];
  ---

... (truncated)

Changelog

Sourced from astro's changelog.

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

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;
    icon: SvgComponent;

... (truncated)

Commits

• a759c1f [ci] release (#14442)
• 1f7ec7d fix: changelog code snippet (#14443)
• a3e16ab fix(astro): invalid font url (#14440)
• 47df8f2 [ci] format
• bdcd9e0 docs: Clarification in ResponseSentError cause (#14391)
• b0cffe7 Fix name of new flag in changelog (#14437)
• 731c07d [ci] release (#14434)
• dcfbd8c feat(types): add SvgComponent type and update SVG module declaration (#13651)
• a98ce3c [ci] format
• a31edb8 feat(core): add routePattern to GetStaticPathsOptions (#13520)
• Additional commits viewable in compare view

Updates sharp from 0.34.3 to 0.34.4

Release notes

Sourced from sharp's releases.

v0.34.4

• Upgrade to libvips v8.17.2 for upstream bug fixes.

• Ensure TIFF subifd and OpenSlide level input options are respected (regression in 0.34.3).

• Ensure autoOrient occurs before non-90 angle rotation. #4425

• Ensure autoOrient removes existing metadata after shrink-on-load. #4431

• TypeScript: Ensure KernelEnum includes linear. #4441 @​BayanBennett

• Ensure unlimited flag is passed upstream when reading TIFF images. #4446

• Support Electron memory cage when reading XMP metadata (regression in 0.34.3). #4451

• Add sharp-libvips rpath for yarn v5 support. #4452 @​arcanis

v0.34.4-rc.4

• Upgrade to libvips v8.17.2 for upstream bug fixes.

• Ensure TIFF subifd and OpenSlide level input options are respected (regression in 0.34.3).

• Ensure autoOrient occurs before non-90 angle rotation. #4425

• Ensure autoOrient removes existing metadata after shrink-on-load. #4431

• TypeScript: Ensure KernelEnum includes linear. #4441 @​BayanBennett

• Ensure unlimited flag is passed upstream when reading TIFF images. #4446

• Support Electron memory cage when reading XMP metadata (regression in 0.34.3). #4451

• Add sharp-libvips rpath for yarn v5 support. #4452 @​arcanis

... (truncated)

Commits

• ee43783 Release v0.34.4
• 5299011 CI/Docs: Deno v2 support
• 4710092 Prerelease v0.34.4-rc.4
• ed1ac43 CI: Upgrade packaging test dependencies
• dfcbcee Upgrade sharp-libvips to v1.2.3
• 35d3f56 Ensure TIFF subifd and OpenSlide level are respected
• 9f4bace Prerelease v0.34.4-rc.3
• b507831 CI: Remove dry-run flag
• 905f698 Prerelease v0.34.4-rc.2
• b0154ed Upgrade sharp-libvips to v1.2.2
• 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 sharp 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

[cloudflare-workers-and-pages]

Deploying htmlhint with    Cloudflare Pages

Latest commit:	e9e66d9
Status:	✅  Deploy successful!
Preview URL:	https://d333fa18.htmlhint.pages.dev
Branch Preview URL:	https://dependabot-npm-and-yarn-webs-vrwo.htmlhint.pages.dev

View logs