chore(deps): update non-major

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/starlight (source)	0.29.3 -> 0.30.3
starlight-blog (source)	0.15.0 -> 0.16.1
starlight-links-validator (source)	0.13.4 -> 0.14.1

---

Warning

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

---

Release Notes

withastro/starlight (@​astrojs/starlight)

v0.30.3

Compare Source

Patch Changes

• #​2717 c5fcbb3 Thanks @​delucis! - Fixes a list item spacing issue where line break elements (<br>) could receive a margin, breaking layout in Firefox

• #​2724 02d7ac6 Thanks @​dionysuzx! - Adds social link support for Farcaster

• #​2635 ec4b851 Thanks @​HiDeoo! - Fixes an issue where the language picker in multilingual sites could display the wrong language when navigating between pages with the browser back/forward buttons.

• #​2726 e54ebd5 Thanks @​techfg! - Adds icon for phone

v0.30.2

Compare Source

Patch Changes

• #​2702 02d16f3 Thanks @​HiDeoo! - Fixes an issue with autogenerated sidebars when using Starlight with Astro's new Content Layer API with directories containing spaces or special characters.

• #​2704 fd16470 Thanks @​delucis! - Fixes display of focus indicator around site title

v0.30.1

Compare Source

Patch Changes

• #​2688 5c6996c Thanks @​HiDeoo! - Fixes an issue with autogenerated sidebars when using Starlight with Astro's new Content Layer API where group names would be sluggified.

v0.30.0

Compare Source

Minor Changes

• #​2612 8d5a4e8 Thanks @​HiDeoo! - Adds support for Astro v5, drops support for Astro v4.

Upgrade Astro and dependencies

⚠️ BREAKING CHANGE: Astro v4 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 v5. 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: Starlight's internal content collections, which organize, validate, and render your content, have been updated to use Astro's new Content Layer API and require configuration changes in your project.

1. Move the content config file. This file no longer lives within the src/content/config.ts folder and should now exist at src/content.config.ts.

2. Edit the collection definition(s). To update the docs collection, a loader is now required:

    // src/content.config.ts
    import { defineCollection } from "astro:content";
   +import { docsLoader } from "@​astrojs/starlight/loaders";
    import { docsSchema } from "@​astrojs/starlight/schema";
   
    export const collections = {
   -  docs: defineCollection({ schema: docsSchema() }),
   +  docs: defineCollection({ loader: docsLoader(), schema: docsSchema() }),
    };

   If you are using the i18n collection to provide translations for additional languages you support or override our default labels, you will need to update the collection definition in a similar way and remove the collection type which is no longer available:

    // src/content.config.ts
    import { defineCollection } from "astro:content";
   +import { docsLoader, i18nLoader } from "@​astrojs/starlight/loaders";
    import { docsSchema, i18nSchema } from "@​astrojs/starlight/schema";
   
    export const collections = {
   -  docs: defineCollection({ schema: docsSchema() }),
   +  docs: defineCollection({ loader: docsLoader(), schema: docsSchema() }),
   -  i18n: defineCollection({ type: 'data', schema: i18nSchema() }),
   +  i18n: defineCollection({ loader: i18nLoader(), schema: i18nSchema() }),
    };

3. Update other collections. To update any other collections you may have, follow the “Updating existing collections” section in the Astro 5 upgrade guide.

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.collections flag to upgrade to v5 without updating your collections. This legacy flag exists to provide temporary backwards compatibility, and will allow you to keep your collections in their current state until the legacy flag is no longer supported.

Patch Changes

• #​2669 310df7d Thanks @​aaronperezaguilera! - Adds Catalan UI translations

• #​2664 62ff007 Thanks @​HiDeoo! - Publishes provenance containing verifiable data to link a package back to its source repository and the specific build instructions used to publish it.

• #​2670 0223b42 Thanks @​aaronperezaguilera! - Adds Spanish UI translations for the Pagefind search modal

HiDeoo/starlight-blog (starlight-blog)

v0.16.1

Compare Source

Patch Changes

• #​105 4ce050c Thanks @​HiDeoo! - Adds support for passing Infinity to the postCount and recentPostCount configuration options.

v0.16.0

Compare Source

Minor Changes

• #​100 679e509 Thanks @​HiDeoo! - Adds support for Astro v5, drops support for Astro v4.

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

  Please follow the upgrade guide to update your project.

  Note that the legacy.collections flag is not supported by this plugin and you should update your collections to use Astro's new Content Layer API.

  ⚠️ BREAKING CHANGE: The generated RSS feed no longer includes content of blog posts due to a regression in Astro v5. The feature will be restored in a future release. If you rely on this feature, please stay on a previous version of Starlight and Astro in the meantime.

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

v0.14.1

Compare Source

Patch Changes

• #​82 b3cbee8 Thanks @​HiDeoo! - Fixes regresion introduced in version 0.14.0 of the plugin regarding validation of links to pages with custom IDs/slugs.

  Note that you must use at least Astro version 5.1.1 to benefit from this fix.

• #​80 876cb50 Thanks @​lukekarrys! - Fixes validation issues for pages ending in index, e.g. module_index.

v0.14.0

Compare Source

Minor Changes

• #​77 486a379 Thanks @​HiDeoo! - Adds support for Astro v5, drops support for Astro v4.

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

  Please follow the upgrade guide to update your project.

  When using the plugin with the Content Layer API, the plugin will now automatically invalidate the content layer cache so that all links can be properly validated. To avoid unnecessary cache invalidation, it is recommended to conditionally use the plugin only when necessary. Check out the new “Conditional Validation” guide for more information.

  ⚠️ BREAKING CHANGE: Due to a regression in Astro v5, links to pages with custom IDs/slugs can no longer be validated and will be flagged as invalid. If you rely on this feature, please stay on a previous version of Starlight and Astro in the meantime.

---

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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/astro
npm error   astro@"4.16.18" from the root project
npm error
npm error Could not resolve dependency:
npm error peer astro@"^5.0.0" from @astrojs/[email protected]
npm error node_modules/@astrojs/starlight
npm error   @astrojs/starlight@"0.30.3" 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 /tmp/renovate/cache/others/npm/_logs/2024-12-22T12_18_47_446Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-22T12_18_47_446Z-debug-0.log