Releases: HiDeoo/starlight-links-validator
starlight-links-validator@0.14.1
Patch Changes
-
#82
b3cbee8
Thanks @HiDeoo! - Fixes regresion introduced in version0.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 inindex
, e.g.module_index
.
starlight-links-validator@0.14.0
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 now0.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.
v0.13.4
🐞 Bug Fixes
- Fixes a validation issue with Markdown headings including trailing markup - by @jorenbroekema and @HiDeoo (009be)
View changes on GitHub
v0.13.3
🚀 Features
- Improves messages for errors related to the Astro
trailingSlash
option to indicate if a link is missing a trailing slash or if a link has a trailing slash when it should not - by @HiDeoo (a8776)
View changes on GitHub
v0.13.2
🐞 Bug Fixes
View changes on GitHub
v0.13.1
🐞 Bug Fixes
- Refactors some internal types to prevent type issues with future Starlight versions - by @HiDeoo (11518)
View changes on GitHub
v0.13.0
🚨 Breaking Changes
-
Adds errors for local links, e.g. URLs with a hostname of
localhost
or127.0.0.1
- by @HiDeoo (80636)In previous versions, such links were silently ignored. They are now considered as invalid links as they are usually used for development purposes and should not be present in production.
If you want to preserve the previous behaviour, you can set theerrorOnLocalLinks
option tofalse
in yourastro.config.mjs
file:export default defineConfig({ integrations: [ starlight({ plugins: [ starlightLinksValidator({ errorOnLocalLinks: false, }), ], }), ], });