Skip to content

fix(deps): update npm-packages [skip ci] #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update npm-packages [skip ci] #26

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link

@renovate renovate bot commented Sep 8, 2025 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/starlight (source) ^0.33.0 -> ^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
astro (source) ^5.6.1 -> ^5.16.6 age adoption passing confidence
prettier (source) 3.6.2 -> 3.7.4 age adoption passing confidence
sharp (source, changelog) ^0.33.5 -> ^0.34.5 age adoption passing confidence
starlight-contributor-list (source) ^0.3.0 -> ^0.3.1 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.

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.

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
withastro/astro (astro)

v5.16.6

Compare Source

Patch Changes

v5.16.5

Compare Source

Patch Changes

  • #​14985 c016f10 Thanks @​florian-lefebvre! - Fixes a case where JSDoc annotations wouldn't show for fonts related APIs in the Astro config

  • #​14973 ed7cc2f Thanks @​amankumarpandeyin! - Fixes performance regression and OOM errors when building medium-sized blogs with many content entries. Replaced O(n²) object spread pattern with direct mutation in generateLookupMap.

  • #​14958 70eb542 Thanks @​ascorbic! - Gives a helpful error message if a user sets output: "hybrid" in their Astro config.

    The option was removed in Astro 5, but lots of content online still references it, and LLMs often suggest it. It's not always clear that the replacement is output: "static", rather than output: "server". This change adds a helpful error message to guide humans and robots.

  • #​14901 ef53716 Thanks @​Darknab! - Updates the glob() loader to log a warning when duplicated IDs are detected

  • Updated dependencies [d8305f8]:

v5.16.4

Compare Source

Patch Changes

  • #​14940 2cf79c2 Thanks @​ematipico! - Fixes a bug where Astro didn't properly combine CSP resources from the csp configuration with those added using the runtime API (Astro.csp.insertDirective()) to form grammatically correct CSP headers

    Now Astro correctly deduplicate CSP resources. For example, if you have a global resource in the configuration file, and then you add a
    a new one using the runtime APIs.

v5.16.3

Compare Source

Patch Changes

  • #​14889 4bceeb0 Thanks @​florian-lefebvre! - Fixes actions types when using specific TypeScript configurations

  • #​14929 e0f277d Thanks @​matthewp! - Fixes authentication bypass via double URL encoding in middleware

    Prevents attackers from bypassing path-based authentication checks using multi-level URL encoding (e.g., /%2561dmin instead of /%61dmin). Pathnames are now validated after decoding to ensure no additional encoding remains.

v5.16.2

Compare Source

Patch Changes

v5.16.1

Compare Source

Patch Changes

v5.16.0

Compare Source

Minor Changes

  • #​13880 1a2ed01 Thanks @​azat-io! - Adds experimental SVGO optimization support for SVG assets

    Astro now supports automatic SVG optimization using SVGO during build time. This experimental feature helps reduce SVG file sizes while maintaining visual quality, improving your site's performance.

    To enable SVG optimization with default settings, add the following to your astro.config.mjs:

    import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    svgo: true,
  },
});

    To customize optimization, pass a SVGO configuration object:

    export default defineConfig({
  experimental: {
    svgo: {
      plugins: [
        'preset-default',
        {
          name: 'removeViewBox',
          active: false,
        },
      ],
    },
  },
});

    For more information on enabling and using this feature in your project, see the experimental SVG optimization docs.

  • #​14810 2e845fe Thanks @​ascorbic! - Adds a hint for code agents to use the --yes flag to skip prompts when running astro add

  • #​14698 f42ff9b Thanks [@​mauriciabad](https://redirect.github.com/m

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 23:23
@changeset-bot
Copy link

changeset-bot bot commented Sep 8, 2025 •
edited
Loading

⚠️ No Changeset found

Latest commit: ed466f2

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-sidebar-swipe-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

coderabbitai bot commented Sep 8, 2025 •
edited
Loading

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 dacbb5f to 1dd2ea6 Compare September 14, 2025 12:07
@renovate renovate bot force-pushed the renovate/npm-packages branch 3 times, most recently from df2a671 to fbe6801 Compare September 23, 2025 20:08
@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from 4bc3b93 to 315e7d4 Compare September 26, 2025 15:56
@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from 8562e2c to fa6758f Compare October 15, 2025 19:45
@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from 45e56df to 68ada79 Compare October 23, 2025 06:41
@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from 864ee8e to ff98977 Compare October 31, 2025 20:39
@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from f3e18c0 to ab0db77 Compare November 8, 2025 11:47
@renovate renovate bot force-pushed the renovate/npm-packages branch 3 times, most recently from 515848c to cea52b0 Compare November 19, 2025 07:44
@renovate renovate bot force-pushed the renovate/npm-packages branch 4 times, most recently from 2a60fe7 to ee8c0f8 Compare November 28, 2025 20:01
@renovate renovate bot force-pushed the renovate/npm-packages branch 3 times, most recently from 9f420fe to cf2ec09 Compare December 4, 2025 00:15
@renovate renovate bot force-pushed the renovate/npm-packages branch from cf2ec09 to 81744a8 Compare December 11, 2025 12:09
@renovate renovate bot force-pushed the renovate/npm-packages branch from 81744a8 to ed466f2 Compare December 18, 2025 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@trueberryless trueberryless Awaiting requested review from trueberryless

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant