[Snyk] Upgrade @astrojs/starlight from 0.28.6 to 0.34.3

[nerdy-tech-com-gitub]

Snyk has created this PR to upgrade @astrojs/starlight from 0.28.6 to 0.34.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 27 versions ahead of your current version.

• The recommended version was released a month ago.

Release notes

Package name: @astrojs/starlight

• 0.34.3 - 2025-05-08
  

  Patch Changes

  • #3058 274cc06 Thanks @ techfg! - Fixes display of focus indicator around site title

  • #3181 449c822 Thanks @ HiDeoo! - Fixes an issue where all headings in Markdown and MDX content were rendered with a clickable anchor link, even in non-Starlight pages.

  • #3168 ca693fe Thanks @ jsparkdev! - Updates Korean langage support with improvements and missing translations

• 0.34.2 - 2025-05-01
  

  Patch Changes

  • #3153 ea31f46 Thanks @ SuperKXT! - Fixes hover styles for highlighted directory in FileTree component.

  • #2905 b5232bc Thanks @ HiDeoo! - Fixes a potential issue for projects with dynamic routes added by an user, an Astro integration, or a Starlight plugin where some styles could end up being missing.

  • #3165 80a7871 Thanks @ KianNH! - Increases maxBuffer for an internal spawnSync() call to support larger Git commit histories when using Starlight's lastUpdated feature.

  • #3158 d1f3c8b Thanks @ heisenberg0924! - Adds Hungarian language support

• 0.34.1 - 2025-04-24
  

  Patch Changes

  • #3140 f6eb1d5 Thanks @ HiDeoo! - Fixes a text selection issue for heading with a clickable anchor link when using double or triple click to select text.

  • #3148 dc8b6d5 Thanks @ HiDeoo! - Fixes a regression of the Starlight icon color when using the credits configuration option.

• 0.34.0 - 2025-04-16
  

  Minor Changes

  • #2322 f14eb0c Thanks @ HiDeoo! - Groups all of Starlight's CSS declarations into a single starlight cascade layer.

    This change allows for easier customization of Starlight's CSS as any custom unlayered CSS will override the default styles. If you are using cascade layers in your custom CSS, you can use the @ layer CSS at-rule to define the order of precedence for different layers including the ones used by Starlight.

    We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.

  • #3122 3a087d8 Thanks @ delucis! - Removes default attrs and content values from head entries parsed using Starlight’s schema.

    Previously when adding head metadata via frontmatter or user config, Starlight would automatically add values for attrs and content if not provided. Now, these properties are left undefined.

    This makes it simpler to add tags in route middleware for example as you no longer need to provide empty values for attrs and content:

    head.push({
      tag: 'style',
      content: 'div { color: red }'
    - attrs: {},
    });
    head.push({
      tag: 'link',
    - content: ''
      attrs: { rel: 'me', href: 'https://example.com' },
    });

    This is mostly an internal API but if you are overriding Starlight’s Head component or processing head entries in some way, you may wish to double check your handling of Astro.locals.starlightRoute.head is compatible with attrs and content potentially being undefined.

  • #3033 8c19678 Thanks @ delucis! - Adds support for generating clickable anchor links for headings.

    By default, Starlight now renders an anchor link beside headings in Markdown and MDX content. A new <AnchorHeading> component is available to achieve the same thing in custom pages built using <StarlightPage>.

    If you want to disable this new Markdown processing set the markdown.headingLinks option in your Starlight config to false:

    starlight({
      title: 'My docs',
      markdown: {
        headingLinks: false,
      },
    }),

    ⚠️ BREAKING CHANGE: The minimum supported version of Astro is now v5.5.0.

    Please update Starlight and Astro together:

    npx @ astrojs/upgrade

  • #2322 f14eb0c Thanks @ HiDeoo! - Removes Shiki css-variables theme fallback.

    ⚠️ BREAKING CHANGE:

    Previously, Starlight used to automatically provide a fallback theme for Shiki, the default syntax highlighter built into Astro if the configured Shiki theme was not github-dark.

    This fallback was only relevant when the default Starlight code block renderer, Expressive Code, was disabled and Shiki was used. Starlight no longer provides this fallback.

    If you were relying on this behavior, you now manually need to update your Astro configuration to use the Shiki css-variables theme to match the previous behavior.

    + markdown: {
    + shikiConfig: {
    + theme: 'css-variables',
    + },
    + },
    });

    Additionally, you can use custom CSS to control the appearance of the code blocks. Here are the previously used CSS variables for the fallback theme:

    :root {
      --astro-code-foreground: var(--sl-color-white);
      --astro-code-background: var(--sl-color-gray-6);
      --astro-code-token-constant: var(--sl-color-blue-high);
      --astro-code-token-string: var(--sl-color-green-high);
      --astro-code-token-comment: var(--sl-color-gray-2);
      --astro-code-token-keyword: var(--sl-color-purple-high);
      --astro-code-token-parameter: var(--sl-color-red-high);
      --astro-code-token-function: var(--sl-color-red-high);
      --astro-code-token-string-expression: var(--sl-color-green-high);
      --astro-code-token-punctuation: var(--sl-color-gray-2);
      --astro-code-token-link: var(--sl-color-blue-high);
    }

  Patch Changes

  • #3118 77a1104 Thanks @ delucis! - Fixes passing imported SVGs to the frontmatter prop of the <StarlightPage> component in Astro ≥5.7.0
• 0.33.2 - 2025-04-14
  

  Patch Changes

  • #3090 fc3ffa8 Thanks @ delucis! - Updates internal @ astrojs/mdx, @ astrojs/sitemap, and astro-expressive-code dependencies

  • #3109 b5cc1b4 Thanks @ dhruvkb! - Updates Expressive Code to v0.41.1

• 0.33.1 - 2025-04-11
• 0.33.0 - 2025-04-07
• 0.32.6 - 2025-04-05
• 0.32.5 - 2025-03-26
• 0.32.4 - 2025-03-21
• 0.32.3 - 2025-03-18
• 0.32.2 - 2025-02-27
• 0.32.1 - 2025-02-19
• 0.32.0 - 2025-02-15
• 0.31.1 - 2025-01-17
• 0.31.0 - 2025-01-13
• 0.30.6 - 2025-01-10
• 0.30.5 - 2025-01-07
• 0.30.4 - 2025-01-06
• 0.30.3 - 2024-12-19
• 0.30.2 - 2024-12-16
• 0.30.1 - 2024-12-14
• 0.30.0 - 2024-12-13
• 0.29.3 - 2024-12-11
• 0.29.2 - 2024-11-19
• 0.29.1 - 2024-11-19
• 0.29.0 - 2024-11-08
• 0.28.6 - 2024-11-04

from @astrojs/starlight GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Chores:

• Bump @astrojs/starlight version in package.json to ^0.34.3

[sourcery-ai]

Reviewer's Guide

This PR bumps the @astrojs/starlight dependency to v0.34.3 in the basic examples package.json, ensuring the project uses the latest patched version of Starlight.

File-Level Changes

Change	Details	Files
Upgrade @astrojs/starlight dependency	Updated version specifier from ^0.28.3 to ^0.34.3	examples/basics/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.