Skip to content

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 15, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/starlight (source) ^0.32.2 -> ^0.36.0 age confidence
sharp (source, changelog) ^0.32.5 -> ^0.34.0 age confidence

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:

    .tab > [role='tab'] {
      line-height: var(--sl-line-height);
      padding-block: 0;
    }
  • #​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 some content which generates invalid HTML as <meta> is a void element which cannot have any child nodes. Now, it is an error to define a meta tag including some content.

    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 a content property for a meta tag. To fix the error, move the content property to the attrs object 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 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.

    .my-custom-component {
      margin-top: 0;
    }
Patch Changes
  • #​3423 a0d0670 Thanks @​andersk! - Fixes HTML validity in sidebar groups by ensuring <summary> is the first child of <details>

v0.35.3

Compare Source

Patch Changes

v0.35.2

Compare Source

Patch Changes
  • #​3341 10f6fe2 Thanks @​HiDeoo! - Prevents potential build issues with the Astro Cloudflare adapter due to the dependency on Node.js builtins.

  • #​3327 bf58c60 Thanks @​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.

v0.35.1

Compare Source

Patch Changes

v0.35.0

Compare Source

Minor Changes
  • #​2261 778b743 Thanks @​shubham-padia! - Adds support for using any of Starlight’s built-in icons in asides.

  • #​3272 e7fe267 Thanks @​delucis! - Adds a new generateId option to Starlight’s docsLoader()

    This enables overriding the default sluggifier used to convert content filenames to URLs.

  • #​3276 3917b20 Thanks @​delucis! - Excludes banner content from search results

    Previously, content set in banner in page frontmatter was indexed by Starlight’s default search provider Pagefind. This could cause unexpected search results, especially for sites setting a common banner content on multiple pages. Starlight’s default Banner component is now excluded from search indexing.

    This change does not impact Banner overrides using custom components.

  • #​3266 1161af0 Thanks @​HiDeoo! - Adds support for custom HTML attributes on autogenerated sidebar links using the autogenerate.attrs option.

  • #​3274 80ccff7 Thanks @​HiDeoo! - Fixes an issue where some Starlight remark and rehype plugins were transforming Markdown and MDX content in non-Starlight pages.

    ⚠️ BREAKING CHANGE:

    Previously, some of Starlight’s remark and rehype plugins, most notably the plugin transforming Starlight's custom Markdown syntax for rendering asides, were applied to all Markdown and MDX content. This included content from individual Markdown pages and content from content collections other than the docs collection used by Starlight.

    This change restricts the application of Starlight’s remark and rehype plugins to only Markdown and MDX content loaded using Starlight's docsLoader(). If you were relying on this behavior, please let us know about your use case in the dedicated #starlight channel in the Astro Discord or by opening an issue.

Patch Changes
  • #​3266 1161af0 Thanks @​HiDeoo! - Ensures invalid sidebar group configurations using the attrs option are properly reported as a type error.

    Previously, invalid sidebar group configurations using the attrs option were not reported as a type error but only surfaced at runtime. This change is only a type-level change and does not affect the runtime behavior of Starlight which does not support the attrs option for sidebar groups.

  • #​3274 80ccff7 Thanks @​HiDeoo! - Prevents Starlight remark and rehype plugins from transforming Markdown and MDX content when using the Astro renderMarkdown() content loader API.

v0.34.8

Compare Source

Patch Changes
  • #​3306 21fcd94 Thanks @​HiDeoo! - Fixes a regression in Starlight version 0.34.5 that caused multilingual sites with a default locale explicitly set to root to report a configuration error.

v0.34.7

Compare Source

Patch Changes

v0.34.6

Compare Source

Patch Changes

v0.34.5

Compare Source

Patch Changes
  • #​3282 7680e87 Thanks @​alvinometric! - Moves padding of <main> element to a --sl-main-pad CSS custom property to simplify setting custom values

  • #​3288 131371e Thanks @​HiDeoo! - Fixes a potential configuration issue for multilingual sites with a default language including a regional subtag.

v0.34.4

Compare Source

Patch Changes

v0.34.3

Compare Source

Patch Changes

v0.34.2

Compare Source

Patch Changes

v0.34.1

Compare Source

Patch Changes
  • #​3140 f6eb1d5 Thanks @​HiDeoo! - Fixes a text selection issue for heading with a clickable anchor link when using double or triple click to select text.

  • #​3148 dc8b6d5 Thanks @​HiDeoo! - Fixes a regression of the Starlight icon color when using the credits configuration option.

v0.34.0

Compare Source

Minor Changes
  • #​2322 f14eb0c Thanks @​HiDeoo! - Groups all of Starlight's CSS declarations into a single starlight cascade layer.

    This change allows for easier customization of Starlight's CSS as any custom unlayered CSS will override the default styles. If you are using cascade layers in your custom CSS, you can use the @layer CSS at-rule to define the order of precedence for different layers including the ones used by Starlight.

    We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.

  • #​3122 3a087d8 Thanks @​delucis! - Removes default attrs and content values from head entries parsed using Starlight’s schema.

    Previously when adding head metadata via frontmatter or user config, Starlight would automatically add values for attrs and content if not provided. Now, these properties are left undefined.

    This makes it simpler to add tags in route middleware for example as you no longer need to provide empty values for attrs and content:

    head.push({
      tag: 'style',
      content: 'div { color: red }'
    - attrs: {},
    });
    head.push({
      tag: 'link',
    - content: ''
      attrs: { rel: 'me', href: 'https://example.com' },
    });

    This is mostly an internal API but if you are overriding Starlight’s Head component or processing head entries in some way, you may wish to double check your handling of Astro.locals.starlightRoute.head is compatible with attrs and content potentially being undefined.

  • #​3033 8c19678 Thanks @​delucis! - Adds support for generating clickable anchor links for headings.

    By default, Starlight now renders an anchor link beside headings in Markdown and MDX content. A new <AnchorHeading> component is available to achieve the same thing in custom pages built using <StarlightPage>.

    If you want to disable this new Markdown processing set the markdown.headingLinks option in your Starlight config to false:

    starlight({
      title: 'My docs',
      markdown: {
        headingLinks: false,
      },
    }),

    ⚠️ BREAKING CHANGE: The minimum supported version of Astro is now v5.5.0.

    Please update Starlight and Astro together:

    npx @&#8203;astrojs/upgrade
  • #​2322 f14eb0c Thanks @​HiDeoo! - Removes Shiki css-variables theme fallback.

    ⚠️ BREAKING CHANGE:

    Previously, Starlight used to automatically provide a fallback theme for Shiki, the default syntax highlighter built into Astro if the configured Shiki theme was not github-dark.

    This fallback was only relevant when the default Starlight code block renderer, Expressive Code, was disabled and Shiki was used. Starlight no longer provides this fallback.

    If you were relying on this behavior, you now manually need to update your Astro configuration to use the Shiki css-variables theme to match the previous behavior.

    import { defineConfig } from 'astro/config';
    
    export default defineConfig({
    + markdown: {
    +   shikiConfig: {
    +     theme: 'css-variables',
    +   },
    + },
    });

    Additionally, you can use custom CSS to control the appearance of the code blocks. Here are the previously used CSS variables for the fallback theme:

    :root {
      --astro-code-foreground: var(--sl-color-white);
      --astro-code-background: var(--sl-color-gray-6);
      --astro-code-token-constant: var(--sl-color-blue-high);
      --astro-code-token-string: var(--sl-color-green-high);
      --astro-code-token-comment: var(--sl-color-gray-2);
      --astro-code-token-keyword: var(--sl-color-purple-high);
      --astro-code-token-parameter: var(--sl-color-red-high);
      --astro-code-token-function: var(--sl-color-red-high);
      --astro-code-token-string-expression: var(--sl-color-green-high);
      --astro-code-token-punctuation: var(--sl-color-gray-2);
      --astro-code-token-link: var(--sl-color-blue-high);
    }
Patch Changes
  • #​3118 77a1104 Thanks @​delucis! - Fixes passing imported SVGs to the frontmatter prop of the <StarlightPage> component in Astro ≥5.7.0

v0.33.2

Compare Source

Patch Changes

v0.33.1

Compare Source

Patch Changes
  • #​3088 1885049 Thanks @​HiDeoo! - Fixes a regression in Starlight version 0.33.0 that caused the description and links to language alternates for multilingual websites to be missing from the <head> of the page.

  • #​3065 463adf5 Thanks @​HiDeoo! - Updates the social configuration option TSDoc example to match the shape of the expected value.

v0.33.0

Compare Source

Minor Changes
  • #​3026 82deb84 Thanks @​HiDeoo! - Fixes a potential list styling issue if the last element of a list item is a <script> tag.

    ⚠️ BREAKING CHANGE:

    This release drops official support for Chromium-based browsers prior to version 105 (released 30 August 2022) and Firefox-based browsers prior to version 121 (released 19 December 2023). You can find a list of currently supported browsers and their versions using this browserslist query.

    With this release, Starlight-generated sites will still work fine on those older browsers except for this small detail in list item styling, but future releases may introduce further breaking changes for impacted browsers, including in patch releases.

  • #​3025 f87e9ac Thanks @​delucis! - Makes social configuration more flexible.

    ⚠️ BREAKING CHANGE: The social configuration option has changed syntax. You will need to update this in astro.config.mjs when upgrading.

    Previously, a limited set of platforms were supported using a shorthand syntax with labels built in to Starlight. While convenient, this approach was less flexible and required dedicated code for each social platform added.

    Now, you must specify the icon and label for each social link explicitly and you can use any of Starlight’s built-in icons for social links.

    The following example shows updating the old social syntax to the new:

    - social: {
    -   github: 'https://github.com/withastro/starlight',
    -   discord: 'https://astro.build/chat',
    - },
    + social: [
    +   { icon: 'github', label: 'GitHub', href: 'https://github.com/withastro/starlight' },
    +   { icon: 'discord', label: 'Discord', href: 'https://astro.build/chat' },
    + ],
  • #​2927 c46904c Thanks @​HiDeoo! - Adds the head route data property which contains an array of all tags to include in the <head> of the current page.

    Previously, the <Head> component was responsible for generating a list of tags to include in the <head> of the current page and rendering them.
    This data is now available as Astro.locals.starlightRoute.head instead and can be modified using route data middleware.
    The <Head> component now only renders the tags provided in Astro.locals.starlightRoute.head.

  • #​2924 6a56d1b Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: Ensures that the <Badge> and <Icon> components no longer render with a trailing space.

    In Astro, components that include styles render with a trailing space which can prevent some use cases from working as expected, e.g. when using such components inlined with text. This change ensures that the <Badge> and <Icon> components no longer render with a trailing space.

    If you were previously relying on that implementation detail, you may need to update your code to account for this change. For example, considering the following code:

    <Badge text="New" />
    Feature

    The rendered text would previously include a space between the badge and the text due to the trailing space automatically added by the component:

    New Feature
    

    Such code will now render the badge and text without a space:

    NewFeature
    

    To fix this, you can add a space between the badge and the text:

    - <Badge text="New" />Feature
    + <Badge text="New" /> Feature
  • #​2727 7c8fa30 Thanks @​techfg! - Updates mobile menu toggle styles to display a close icon while the menu is open

Patch Changes

v0.32.6

Compare Source

Patch Changes

v0.32.5

Compare Source

Patch Changes

v0.32.4

Compare Source

Patch Changes

v0.32.3

Compare Source

Patch Changes
lovell/sharp (sharp)

v0.34.4

Compare Source

  • Upgrade to libvips v8.17.2 for upstream bug fixes.

  • Ensure TIFF subifd and OpenSlide level input options are respected (regression in 0.34.3).

  • Ensure autoOrient occurs before non-90 angle rotation.
    #​4425

  • Ensure autoOrient removes existing metadata after shrink-on-load.
    #​4431

  • TypeScript: Ensure KernelEnum includes linear.
    #​4441
    @​BayanBennett

  • Ensure unlimited flag is passed upstream when reading TIFF images.
    #​4446

  • Support Electron memory cage when reading XMP metadata (regression in 0.34.3).
    #​4451

  • Add sharp-libvips rpath for yarn v5 support.
    #​4452
    @​arcanis

v0.34.3

Compare Source

v0.34.2

Compare Source

v0.34.1

Compare Source

v0.34.0

Compare Source

v0.33.5

Compare Source

v0.33.4

Compare Source

v0.33.3

Compare Source

v0.33.2

Compare Source

v0.33.1

Compare Source

v0.33.0

Compare Source


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 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 renovate bot force-pushed the renovate/all-minor-patch branch from e299b59 to 6a2398d Compare March 15, 2025 04:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 96a06f5 to a80ff39 Compare March 22, 2025 03:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 08e15e4 to ab0d0f0 Compare April 2, 2025 00:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 7070eb5 to 5bff32c Compare April 8, 2025 04:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 4afadc7 to 862c7cd Compare April 18, 2025 04:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from abee83a to bd2f4d3 Compare April 26, 2025 00:01
@ghost
Copy link

ghost commented Apr 26, 2025

Pull Request Revisions

RevisionDescription
r20
Astro package updated to 5.12.3Updated Astro package from version 5.12.0 to 5.12.3 in package-lock.json, bumping to latest minor release
r19
Updated Starlight and dependency versionsIncrementally upgraded multiple dependencies including Starlight from 0.34.x to 0.35.x, Astro from 5.11.x to 5.12.x, Sharp from 0.34.2 to 0.34.3, and various related ecosystem packages
r18
Updated multiple dependency versionsIncrementally updated versions of Astro, Shiki, Expressive Code, and related dependencies to their latest minor releases
r17
Updated Astro and dependency versionsPackage lock updated with newer versions of Astro (5.9.3), Starlight (0.34.4), Astro Compiler (2.12.2), and fdir (6.4.6)
r16
Astro and Compiler version updatesUpdated Astro from 5.9.0 to 5.9.1 and Astro Compiler from 2.12.0 to 2.12.1
15 more revisions
r15
Updated multiple package dependenciesUpgraded packages including Astro, Shiki, and related dependencies to their latest minor versions
r14
Updated dependencies in package-lock.jsonMinor version updates for astro, fdir, and tinyglobby dependencies to their latest patch versions
r13
Package dependencies updated to newer versionsMultiple Astro, Sharp, and related dependencies were incrementally upgraded, including updates to Astro core, MDX, Markdown Remark, and Sharp image processing library.
r12
Updated multiple Shiki and Astro packagesPackage version bumps for Shiki (3.4.0 → 3.4.2), Astro (5.7.12 → 5.7.13), and associated Shiki modules
r11
Updated multiple npm package versionsPackage-lock.json updated with version bumps for Astro, Shiki, Vite, Unifont, and other related dependencies
r10
Updated multiple Astro package versionsUpdated @astrojs/compiler, @astrojs/starlight, and oniguruma-to-es to their latest patch versions
r9
Updated Astro and dependency versionsPackage-lock.json updated with newer versions of Astro, @astrojs/mdx, vite, unifont, and other related dependencies
r8
Updated multiple npm dependency versionsPackage lock file updated with minor version upgrades for several Astro, Shiki, Expressive Code, and related dependencies to their latest point releases
r7
Updated Astro and Vite package versionsPackage-lock.json updated with new versions: Astro from 5.7.3 to 5.7.4 and Vite from 6.3.1 to 6.3.2
r6
Upgraded Starlight and related dependenciesUpdated multiple packages including @astrojs/starlight to version 0.34.0, along with various related dependencies like Astro, Shiki, and other Expressive Code packages
r5
Updated dependency versions in lockfileMultiple dependencies updated, including Starlight, Shiki, Vite, and emnAPI runtime, with minor version increments
r4
Updated Starlight and Sharp dependenciesUpgraded @astrojs/starlight from v0.32.6 to v0.33.0 and sharp from v0.34.0 to v0.34.1
r3
Starlight package version updatedUpdated @astrojs/starlight from version 0.32.5 to 0.32.6 in package-lock.json
r2
Updated Sharp and Astro dependenciesUpgraded Sharp from v0.33.x to v0.34.0 and Astro from v5.6.0 to v5.6.1, with corresponding package-lock updates
r1
Updated Sharp and Astro dependenciesUpgraded Sharp from version 0.32.5 to 0.33.0 and made minor related dependency updates in package.json and package-lock.json

☑️ AI review skipped for r20
Help React with emojis to give feedback on AI-generated reviews:
  • 👍 means the feedback was helpful and actionable
  • 👎 means the feedback was incorrect or unhelpful
💬 Replying to feedback with a comment helps us improve the system. Your input also contributes to shaping future interactions with the AI reviewer.

We'd love to hear from you—reach out anytime at team@review.ai.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from f48a23b to eb22df2 Compare May 3, 2025 11:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from eb22df2 to 577b236 Compare May 10, 2025 00:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 577b236 to 8a97a53 Compare May 17, 2025 07:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 2ac5bf5 to 24b9cc5 Compare May 31, 2025 19:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 4316ff8 to e75c161 Compare June 8, 2025 11:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e75c161 to abf1fe1 Compare June 14, 2025 12:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from abf1fe1 to 31be780 Compare June 21, 2025 20:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 31be780 to e6fbc9c Compare June 29, 2025 12:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e6fbc9c to f9d5ce4 Compare July 6, 2025 15:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f9d5ce4 to f542c05 Compare July 19, 2025 16:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f542c05 to b714381 Compare July 27, 2025 19:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b714381 to 3c85610 Compare August 4, 2025 19:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from fa8bf24 to c8f0b5d Compare August 11, 2025 03:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from ea4e88a to bd5583c Compare August 21, 2025 04:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from bd5583c to 0674fbb Compare September 1, 2025 01:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3a18f8f to f89ee37 Compare September 20, 2025 03:45
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f89ee37 to f8f0856 Compare September 26, 2025 03:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants