chore(deps): update non-major

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/check (source)	0.9.7 → 0.9.8
@astrojs/starlight (source)	0.37.7 → 0.38.2
starlight-blog (source)	0.25.3 → 0.26.1
starlight-links-validator (source)	0.19.2 → 0.20.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

withastro/astro (@​astrojs/check)

v0.9.8

Compare Source

Patch Changes

• #​15892 a2f597d Thanks @​Princesseuh! - Fixes Astro not being able to find astro check sometimes

• Updated dependencies [7b4b254]:

  • @​astrojs/language-server@​2.16.5

withastro/starlight (@​astrojs/starlight)

v0.38.2

Compare Source

Patch Changes

• #​3759 f24ce99 Thanks @​MilesChou! - Fixes an issue where monolingual sites using a region-specific locale (e.g., zh-TW) as the default would incorrectly display base language translations (e.g., zh Simplified Chinese) instead of the region-specific ones (e.g., zh-TW Traditional Chinese).

• #​3768 a4c6c20 Thanks @​delucis! - Improves performance of sidebar generation for sites with very large sidebars

v0.38.1

Compare Source

Patch Changes

• #​3751 fb955ff Thanks @​pyxelr! - Fixes a regression causing global tableOfContents config to be ignored

v0.38.0

Compare Source

Minor Changes

• #​3644 0d2e7ed Thanks @​HiDeoo! - Adds support for Astro v6, drops support for Astro v5.

Upgrade Astro and dependencies

⚠️ BREAKING CHANGE: Astro v5 is no longer supported. Make sure you update Astro and any other official integrations at the same time as updating Starlight:

npx @​astrojs/upgrade

Community Starlight plugins and Astro integrations may also need to be manually updated to work with Astro v6. If you encounter any issues, please reach out to the plugin or integration author to see if it is a known issue or if an updated version is being worked on.

Update your collections

⚠️ BREAKING CHANGE: Drops support for content collections backwards compatibility.

In Astro 5.x, projects could delay upgrading to the new Content Layer API introduced for content collections because of some existing automatic backwards compatibility that was not previously behind a flag. This meant that it was possible to upgrade from Astro 4 to Astro 5 without updating your content collections, even if you had not enabled the legacy.collections flag. Projects would continue to build, and no errors or warnings would be displayed.

Astro v6.0 now removes this automatic legacy content collections support, along with the legacy.collections flag.

If you experience content collections errors after updating to v6, check your project for any removed legacy features that may need updating to the Content Layer API. See the Starlight v0.30.0 upgrade guide for detailed instructions on upgrading legacy collections to the new Content Layer API.

If you are unable to make any changes to your collections at this time, including Starlight's default docs and i18n collections, you can enable the legacy.collectionsBackwardsCompat flag to upgrade to v6 without updating your collections. This temporary flag preserves some legacy v4 content collections features, and will allow you to keep your collections in their current state until the legacy flag is no longer supported.

• #​3704 375edcc Thanks @​florian-lefebvre! - Fixes autocomplete for components exported from @astrojs/starlight/components/*

  ⚠️ Potentially breaking change: This change moves some files used in Starlight’s component internals out of the components/ directory. Direct use of these files was not and is not officially supported. If you previously imported TableOfContents/starlight-toc.ts, TableOfContents/TableOfContentsList.astro, Icons.ts, or SidebarPersistState.ts, please review your code when updating.

• #​3729 3642625 Thanks @​delucis! - Improves Starlight’s default body font stack to better support languages such as Chinese, Japanese, and Korean on Windows.
  For most users there should be no visible change.

  If you would prefer to keep the previous font stack, you can add the following custom CSS to your site:

  :root {
    --sl-font-system: ui-sans-serif, system-ui, 'Segoe UI', Roboto,
      'Helvetica Neue', Arial, 'Noto Sans', sans-serif, 'Apple Color Emoji',
      'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji';
  }

• #​3598 fff38d5 Thanks @​HiDeoo! - Makes hover styles consistent in Starlight’s navigation bar

  Previously, the social icon links and language/theme switchers in Starlight’s navigation bar, dimmed on hover.
  After this change, they now increase in contrast on hover instead.
  This matches hover behavior elsewhere, for example in the sidebar, table of contents, or search button.

  ⚠️ Potentially breaking change: this is a subtle change to the hover style colors.
  If you want to preserve the previous styling, you can add the following custom CSS to your site:

  starlight-theme-select label,
  starlight-lang-select label {
    color: var(--sl-color-gray-1);
  
    &:hover {
      color: var(--sl-color-white);
    }
  }
  
  .social-icons a:hover {
    color: var(--sl-color-text-accent);
    opacity: 0.66;
  }

HiDeoo/starlight-blog (starlight-blog)

v0.26.1

Compare Source

Patch Changes

• #​202 99e3282 Thanks @​julien-deramond! - Fixes a regression in version 0.26.0 preventing to use Infinity as a value for the postCount and recentPostCount configuration options.

v0.26.0

Compare Source

Minor Changes

• #​199 3c6cf12 Thanks @​HiDeoo! - Adds support for Astro v6, drops support for Astro v5.

  ⚠️ BREAKING CHANGE: The minimum supported version of Starlight is now 0.38.0.

  Please follow the upgrade guide to update your project.

• #​201 a3cddb7 Thanks @​HiDeoo! - Adds a new rss configuration option to disable the automatic generation of an RSS feed for the blog when the Astro site option is set.

HiDeoo/starlight-links-validator (starlight-links-validator)

v0.20.1

Compare Source

Patch Changes

• #​139 01c0073 Thanks @​HiDeoo! - Fixes a regression in version 0.20.0 incorrectly reporting non HTTP-based URL links as invalid, e.g. mailto: links.

v0.20.0

Compare Source

Minor Changes

• #​136 7f6b843 Thanks @​HiDeoo! - Adds support for Astro v6, drops support for Astro v5.

  ⚠️ BREAKING CHANGE: The minimum supported version of Starlight is now 0.38.0.

  Please follow the upgrade guide to update your project.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: docs@0.0.1
npm error Found: astro@5.18.1
npm error node_modules/astro
npm error   astro@"5.18.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer astro@"^6.0.0" from @astrojs/starlight@0.38.2
npm error node_modules/@astrojs/starlight
npm error   @astrojs/starlight@"0.38.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-20T20_37_45_415Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-20T20_37_45_415Z-debug-0.log