[Snyk] Upgrade @astrojs/starlight from 0.34.8 to 0.36.2 #403
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade @astrojs/starlight from 0.34.8 to 0.36.2.
ℹ️ 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 7 versions ahead of your current version.
The recommended version was released a month ago.
Release notes
Package name: @astrojs/starlight
-
0.36.2 - 2025-10-31
-
-
-
0.36.1 - 2025-10-15
-
-
-
-
-
0.36.0 - 2025-09-19
-
⚠️ Potentially breaking change: Tab labels now have a narrower line-height and additional vertical padding. If you have custom CSS targetting the
-
⚠️ Potentially breaking change: Previously Starlight would accept a head entry for a
-
⚠️ Potentially breaking change: By default, Starlight applies some vertical spacing (
- #3423
-
0.35.3 - 2025-09-13
-
-
-
-
-
0.35.2 - 2025-07-29
-
-
-
0.35.1 - 2025-07-18
-
0.35.0 - 2025-07-16
-
0.34.8 - 2025-07-16
from @astrojs/starlight GitHub release notesPatch Changes
#3500
7700456Thanks @ delucis! - This is the first release published with OIDC trusted publishing.#3484
620fb38Thanks @ gboubeta-uvigo! - Improves Spanish UI translationsPatch Changes
#3479
2fec483Thanks @ gboubeta-uvigo! - Updates Galician UI translations#3457
c6c0c51Thanks @ HiDeoo! - Deduplicates sitemap link tags in the head.When enabling sitemap in Starlight, a
<link rel="sitemap" href="/sitemap-index.xml">tag is automatically added to the head of each page. Manually specifying sitemap link tags using the Starlightheadconfiguration option or theheadfrontmatter field will now override the default sitemap link tag added by Starlight.This change ensures that users manually adding the
@ astrojs/sitemapintegration to the Astrointegrationsarray for more fine-grained control over sitemap generation and also using thefilenameBaseintegration option can customize the sitemap link tag in the head.#3448
1fc7501Thanks @ dionysuzx! - Enlarges the Farcaster icon to better match other social icons#3473
07204ddThanks @ gboubeta! - Fixes a typo in Galician table of contents labelMinor Changes
#3427
c3b2d0fThanks @ delucis! - Fixes styling of labels that wrap across multiple lines in<Tabs>component<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:
#3380
3364af3Thanks @ HiDeoo! - Makes head entry parsing stricter in Starlight config and content frontmatter.metatag defining somecontentwhich generates invalid HTML as<meta>is a void element which cannot have any child nodes. Now, it is an error to define ametatag including somecontent.If you see errors after updating, look for head entries in the Starlight configuration in the
astro.config.mjsfile or in the frontmatter of your content files that include acontentproperty for ametatag. To fix the error, move thecontentproperty to theattrsobject 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
2018c31Thanks @ HiDeoo! - Adds missing vertical spacing between Markdown content and UI Framework components using client directives.--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.
Patch Changes
a0d0670Thanks @ andersk! - Fixes HTML validity in sidebar groups by ensuring<summary>is the first child of<details>Patch Changes
#3416
fcc0633Thanks @ randomguy-2650! - Updates German UI translations to be more idiomatic.#1640
d1b3828Thanks @ hippotastic! - Refactors various internal systems, improving code quality and maintainability.#3421
97e8103Thanks @ andersk! - Removes an invalidvalueattribute from the language and theme selectors#3422
9200facThanks @ andersk! - Refactors collapsible sidebar sections and “on this page” dropdown to use<span>instead of<div>Patch Changes
#3341
10f6fe2Thanks @ HiDeoo! - Prevents potential build issues with the Astro Cloudflare adapter due to the dependency on Node.js builtins.#3327
bf58c60Thanks @ delucis! - Fixes a routing bug for docs pages with a slug authored with non-normalized composition. This could occur for filenames containing diacritics in some circumstances, causing 404s.Important
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: