Update dependency @astrojs/starlight to ^0.36.0 #28
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/astrojs-starlight-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^0.35.2
->^0.36.0
Release Notes
withastro/starlight (@astrojs/starlight)
v0.36.0
Compare Source
Minor Changes
#3427
c3b2d0f
Thanks @delucis! - Fixes styling of labels that wrap across multiple lines in<Tabs>
component⚠️ Potentially breaking change: Tab labels now have a narrower line-height and additional vertical padding. If you have custom CSS targetting the
<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
3364af3
Thanks @HiDeoo! - Makes head entry parsing stricter in Starlight config and content frontmatter.⚠️ Potentially breaking change: Previously Starlight would accept a head entry for a
meta
tag defining somecontent
which generates invalid HTML as<meta>
is a void element which cannot have any child nodes. Now, it is an error to define ameta
tag including somecontent
.If you see errors after updating, look for head entries in the Starlight configuration in the
astro.config.mjs
file or in the frontmatter of your content files that include acontent
property for ameta
tag. To fix the error, move thecontent
property to theattrs
object with at least an additional attribute to identify the kind of metadata it represents:#3340
2018c31
Thanks @HiDeoo! - Adds missing vertical spacing between Markdown content and UI Framework components using client directives.⚠️ Potentially breaking change: By default, Starlight applies some vertical spacing (
--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
a0d0670
Thanks @andersk! - Fixes HTML validity in sidebar groups by ensuring<summary>
is the first child of<details>
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.