Bump @astrojs/starlight from 0.34.1 to 0.36.0 in /docs

[dependabot]

Bumps @astrojs/starlight from 0.34.1 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

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)

[cloudflare-workers-and-pages]

Deploying replicator with    Cloudflare Pages

Latest commit:	312783b
Status:	🚫  Build failed.

View logs

[dependabot]

Superseded by #202.