Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 8, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/starlight (source) ^0.34.0 -> ^0.37.1 age adoption passing confidence
@astrojs/starlight (source) ^0.34.3 -> ^0.37.1 age adoption passing confidence
@changesets/changelog-github (source) ^0.5.1 -> ^0.5.2 age adoption passing confidence
@changesets/cli (source) ^2.29.7 -> ^2.29.8 age adoption passing confidence
@trueberryless-org/starlight-plugins-docs-components (source) ^0.4.2 -> ^0.4.3 age adoption passing confidence
prettier (source) 3.6.2 -> 3.7.4 age adoption passing confidence
sharp (source, changelog) ^0.34.3 -> ^0.34.5 age adoption passing confidence

Release Notes

withastro/starlight (@​astrojs/starlight)

v0.37.1

Compare Source

Patch Changes
  • #​3603 30f6e7f Thanks @​delucis! - Fixes support for providing an absolute URL to Starlight’s favicon configuration option

v0.37.0

Compare Source

Minor Changes
  • #​3491 28810f0 Thanks @​JusticeMatthew! - Changes text overflow styling in Markdown content

    ⚠️ Potentially breaking change: This release switches the overflow-wrap CSS style for common elements to break-word. In most cases, there should be little visual impact, but this change can impact how layouts with implicit sizing (such as tables) look, improving legibility in how words wrap.

    If you want to preserve the previous styling, you can add the following custom CSS to your site:

    p,
    h1,
    h2,
    h3,
    h4,
    h5,
    h6,
    code {
      overflow-wrap: anywhere;
    }
  • #​3351 239698c Thanks @​HiDeoo! - Ensures that Starlight CSS layer order is predictable in custom pages using the <StarlightPage> component.

    Previously, due to how import order works in Astro, the <StarlightPage> component had to be the first import in custom pages to set up cascade layers used internally by Starlight to manage the order of its styles.

    With this change, this restriction no longer applies and Starlight’s styles will be applied correctly regardless of the import order of the <StarlightPage> component.

  • #​3521 ca7b771 Thanks @​shubham-padia! - Fixes an issue where a vertical scrollbar could be displayed on the Starlight <Tabs> component when zooming the page

    ⚠️ Potentially breaking change: The <Tabs> component no longer uses margin-bottom and border-bottom to highlight the current tab. This is now done with a box-shadow. If you have custom styling for your tabs, you may need to update it.

    If you want to preserve the previous styling, you can add the following custom CSS to your site:

    starlight-tabs .tab {
      margin-bottom: -2px;
    }
    
    starlight-tabs .tab > [role='tab'] {
      border-bottom: 2px solid var(--sl-color-gray-5);
      box-shadow: none;
    }
    
    starlight-tabs .tab [role='tab'][aria-selected='true'] {
      border-color: var(--sl-color-text-accent);
    }
  • #​3549 1cf50eb Thanks @​jacobdalamb! - Updates the default sans-serif system font stack, dropping support for the -apple-system and BlinkMacSystemFont font names used in older browsers. These are no longer needed in browsers officially supported by Starlight.

    If you still need to support older browsers, you can add the following custom CSS to your site:

    :root {
      --sl-font-system: ui-sans-serif, system-ui, -apple-system,
        BlinkMacSystemFont, 'Segoe UI', Roboto, 'Helvetica Neue', Arial,
        'Noto Sans', sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji',
        'Segoe UI Symbol', 'Noto Color Emoji';
    }
  • #​3332 f61f99d Thanks @​HiDeoo! - Adds a new markdown.processedDirs configuration option to specify additional directories where files should be processed by Starlight’s Markdown pipeline.

    By default, Starlight’s processing only applies to Markdown and MDX content loaded using Starlight’s docsLoader(). This new option allows to extend this processing to other directories, which can be useful if you are rendering content from a custom content collection using the <StarlightPage> component and expect Starlight’s Markdown processing to be applied to that content as well.

v0.36.3

Compare Source

Patch Changes
  • #​3555 547dc30 Thanks @​Its-Just-Nans! - Improves the error message thrown when using a file in the public/ directory with Starlight’s customCss configuration option

  • #​3496 b78fda4 Thanks @​delucis! - Fixes invalid <head> output when configuration is missing:

    • Omits <meta property="og:description" /> if Starlight’s description option is unset
    • Omits <link rel="canonical" /> and <meta property="og:url" /> if Astro’s site option is unset
  • #​3511 8727df1 Thanks @​astrobot-houston! - Updates the seti:gitlab icon to match latest version from Seti UI Icons

v0.36.2

Compare Source

Patch Changes

v0.36.1

Compare Source

Patch Changes

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.

changesets/changesets (@​changesets/changelog-github)

v0.5.2

Compare Source

trueberryless-org/starlight-plugins-docs-components (@​trueberryless-org/starlight-plugins-docs-components)

v0.4.3

Compare Source

Patch Changes
prettier/prettier (prettier)

v3.7.4

Compare Source

diff

LWC: Avoid quote around interpolations (#​18383 by @​kovsu)
<!-- Input -->
<div foo={bar}>   </div>

<!-- Prettier 3.7.3 (--embedded-language-formatting off) -->
<div foo="{bar}"></div>

<!-- Prettier 3.7.4 (--embedded-language-formatting off) -->
<div foo={bar}></div>
TypeScript: Fix comment inside union type gets duplicated (#​18393 by @​fisker)
// Input
type Foo = (/** comment */ a | b) | c;

// Prettier 3.7.3
type Foo = /** comment */ (/** comment */ a | b) | c;

// Prettier 3.7.4
type Foo = /** comment */ (a | b) | c;
TypeScript: Fix unstable comment print in union type comments (#​18395 by @​fisker)
// Input
type X = (A | B) & (
  // comment
  A | B
);

// Prettier 3.7.3 (first format)
type X = (A | B) &
  (// comment
  A | B);

// Prettier 3.7.3 (second format)
type X = (
  | A
  | B // comment
) &
  (A | B);

// Prettier 3.7.4
type X = (A | B) &
  // comment
  (A | B);

v3.7.3

Compare Source

diff

API: Fix prettier.getFileInfo() change that breaks VSCode extension (#​18375 by @​fisker)

An internal refactor accidentally broke the VSCode extension plugin loading.

v3.7.2

Compare Source

diff

JavaScript: Fix string print when switching quotes (#​18351 by @​fisker)
// Input
console.log("A descriptor\\'s .kind must be \"method\" or \"field\".")

// Prettier 3.7.1
console.log('A descriptor\\'s .kind must be "method" or "field".');

// Prettier 3.7.2
console.log('A descriptor\\\'s .kind must be "method" or "field".');
JavaScript: Preserve quote for embedded HTML attribute values (#​18352 by @​kovsu)
// Input
const html = /* HTML */ ` <div class="${styles.banner}"></div> `;

// Prettier 3.7.1
const html = /* HTML */ ` <div class=${styles.banner}></div> `;

// Prettier 3.7.2
const html = /* HTML */ ` <div class="${styles.banner}"></div> `;
TypeScript: Fix comment in empty type literal (#​18364 by @​fisker)
// Input
export type XXX = {
  // tbd
};

// Prettier 3.7.1
export type XXX = { // tbd };

// Prettier 3.7.2
export type XXX = {
  // tbd
};

v3.7.1

Compare Source

diff

API: Fix performance regression in doc printer (#​18342 by @​fisker)

Prettier 3.7.1 can be very slow when formatting big files, the regression has been fixed.

v3.7.0

Compare Source

diff

🔗 Release Notes

lovell/sharp (sharp)

v0.34.5

Compare Source

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

  • Add experimental support for prebuilt Linux RISC-V 64-bit binaries.

  • Support building from source with npm v12+, deprecate --build-from-source flag.
    #​4458

  • Add support for BigTIFF output.
    #​4459
    @​throwbi

  • Improve error messaging when only warnings issued.
    #​4465

  • Simplify ICC processing when retaining input profiles.
    #​4468

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


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 requested a review from trueberryless as a code owner September 8, 2025 22:28
@changeset-bot
Copy link

changeset-bot bot commented Sep 8, 2025

⚠️ No Changeset found

Latest commit: b5f336d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR
Some errors occurred when validating the changesets config:
The package or glob expression "starlight-theme-next-docs" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 8, 2025

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (1)
  • [skip ci]

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot added 🌏 i18n Updates to internationalized docs, excluding English 📦 package Updates in package structure or package.json labels Sep 8, 2025
@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from e9abab4 to d5648e8 Compare September 13, 2025 20:58
@renovate renovate bot force-pushed the renovate/npm-packages branch 4 times, most recently from 9a1e0f4 to 6fbfaa9 Compare September 22, 2025 14:14
@renovate renovate bot force-pushed the renovate/npm-packages branch 3 times, most recently from 84dc89e to 3d2fddd Compare September 26, 2025 12:29
@renovate renovate bot force-pushed the renovate/npm-packages branch 4 times, most recently from afed65c to 184d017 Compare October 15, 2025 15:47
@renovate renovate bot force-pushed the renovate/npm-packages branch from 184d017 to 1a9b23c Compare October 21, 2025 09:32
@renovate renovate bot force-pushed the renovate/npm-packages branch 4 times, most recently from 4100452 to 832a8d0 Compare November 6, 2025 17:56
@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from 262b8be to 56232f0 Compare November 24, 2025 21:32
@renovate renovate bot force-pushed the renovate/npm-packages branch 5 times, most recently from e87a378 to f310c2f Compare November 29, 2025 01:36
@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from ea5f998 to 64a1f50 Compare December 3, 2025 08:35
@renovate renovate bot force-pushed the renovate/npm-packages branch from 64a1f50 to b5f336d Compare December 10, 2025 02:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🌏 i18n Updates to internationalized docs, excluding English 📦 package Updates in package structure or package.json

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant