Skip to content

fix(deps): update astro & starlight packages #3306

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
Draft
wants to merge 1 commit into
base: v2
Choose a base branch
from
Draft

fix(deps): update astro & starlight packages #3306

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 26, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/markdown-remark (source) ^5.2.0 -> ^6.0.0 age adoption passing confidence
@astrojs/rss (source) 4.0.11 -> 4.0.12 age adoption passing confidence
@astrojs/starlight (source) 0.29.2 -> 0.34.3 age adoption passing confidence
@lorenzo_lewis/starlight-utils (source) ^0.2.0 -> ^0.3.0 age adoption passing confidence
astro (source) ^4.16.18 -> ^5.0.0 age adoption passing confidence
astro-d2 (source) ^0.6.0 -> ^0.8.0 age adoption passing confidence
starlight-blog (source) ^0.15.0 -> ^0.24.0 age adoption passing confidence
starlight-links-validator (source) ^0.13.0 -> ^0.16.0 age adoption passing confidence
typedoc (source) ^0.26.6 -> ^0.28.0 age adoption passing confidence
typedoc-plugin-markdown (source) 4.2.10 -> 4.6.4 age adoption passing confidence
typedoc-plugin-mdn-links ^3.2.11 -> ^5.0.0 age adoption passing confidence

Release Notes

withastro/astro (@​astrojs/markdown-remark)

v6.3.2

Patch Changes

v6.3.1

Patch Changes

v6.3.0

Compare Source

Minor Changes

  • #​13352 cb886dc Thanks @​delucis! - Adds support for a new experimental.headingIdCompat flag

    By default, Astro removes a trailing - from the end of IDs it generates for headings ending with
    special characters. This differs from the behavior of common Markdown processors.

    You can now disable this behavior with a new configuration flag:

    // astro.config.mjs
import { defineConfig } from 'astro/config';

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

    This can be useful when heading IDs and anchor links need to behave consistently across your site
    and other platforms such as GitHub and npm.

    If you are using the rehypeHeadingIds plugin directly, you can also pass this new option:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import { rehypeHeadingIds } from '@​astrojs/markdown-remark';
import { otherPluginThatReliesOnHeadingIDs } from 'some/plugin/source';

export default defineConfig({
  markdown: {
    rehypePlugins: [
      [rehypeHeadingIds, { experimentalHeadingIdCompat: true }],
      otherPluginThatReliesOnHeadingIDs,
    ],
  },
});

  • #​13311 a3327ff Thanks @​chrisirhc! - Adds a new configuration option for Markdown syntax highlighting excludeLangs

    This option provides better support for diagramming tools that rely on Markdown code blocks, such as Mermaid.js and D2 by allowing you to exclude specific languages from Astro's default syntax highlighting.

    This option allows you to avoid rendering conflicts with tools that depend on the code not being highlighted without forcing you to disable syntax highlighting for other code blocks.

    The following example configuration will exclude highlighting for mermaid and math code blocks:

    import { defineConfig } from 'astro/config';

export default defineConfig({
  markdown: {
    syntaxHighlight: {
      type: 'shiki',
      excludeLangs: ['mermaid', 'math'],
    },
  },
});

    Read more about this new option in the Markdown syntax highlighting configuration docs.

v6.2.1

Compare Source

Patch Changes

v6.2.0

Compare Source

Minor Changes

  • #​13254 1e11f5e Thanks @​p0lyw0lf! - Adds remote image optimization in Markdown

    Previously, an internal remark plugin only looked for images in ![]() syntax that referred to a relative file path. This meant that only local images stored in src/ were passed through to an internal rehype plugin that would transform them for later processing by Astro's image service.

    Now, the plugins recognize and transform both local and remote images using this syntax. Only authorized remote images specified in your config are transformed; remote images from other sources will not be processed.

    While not configurable at this time, this process outputs two separate metadata fields (localImagePaths and remoteImagePaths) which allow for the possibility of controlling the behavior of each type of image separately in the future.

Patch Changes

v6.1.0

Compare Source

Minor Changes

  • #​12850 db252e0 Thanks @​colinbate! - Adds support for TOML frontmatter in .md and .mdx files

    Astro 5.2 automatically identifies the format of your Markdown and MDX frontmatter based on the delimiter used. With +++ as a delimiter (instead of the --- YAML code fence), your frontmatter will automatically be recognized and parsed as TOML.

    This is useful for adding existing content files with TOML frontmatter to your project from another framework such as Hugo.

    TOML frontmatter can also be used with content collections, and files with different frontmatter languages can live together in the same project.

    No configuration is required to use TOML frontmatter in your content files. Your delimiter will indicate your chosen frontmatter language:

    +++
date = 2025-01-30
title = 'Use TOML frontmatter in Astro!'
[author]
name = 'Colin Bate'
+++

v6.0.2

Compare Source

Patch Changes

v6.0.1

Compare Source

Patch Changes

v6.0.0

Compare Source

Major Changes

  • #​11861 3ab3b4e Thanks @​bluwy! - Cleans up Astro-specific metadata attached to vfile.data in Remark and Rehype plugins. Previously, the metadata was attached in different locations with inconsistent names. The metadata is now renamed as below:

    • vfile.data.__astroHeadings -> vfile.data.astro.headings
    • vfile.data.imagePaths -> vfile.data.astro.imagePaths

    The types of imagePaths has also been updated from Set<string> to string[]. The vfile.data.astro.frontmatter metadata is left unchanged.

    While we don't consider these APIs public, they can be accessed by Remark and Rehype plugins that want to re-use Astro's metadata. If you are using these APIs, make sure to access them in the new locations.

  • #​12008 5608338 Thanks @​Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

    Starting from this release, no breaking changes will be introduced unless absolutely necessary.

    To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

  • #​11825 560ef15 Thanks @​bluwy! - Updates return object of createShikiHighlighter as codeToHast and codeToHtml to allow generating either the hast or html string directly

  • #​11661 83a2a64 Thanks @​bluwy! - Renames the following CSS variables theme color token names to better align with the Shiki v1 defaults:

    • --astro-code-color-text => --astro-code-foreground
    • --astro-code-color-background => --astro-code-background

    You can perform a global find and replace in your project to migrate to the new token names.

  • #​11861 3ab3b4e Thanks @​bluwy! - Removes InvalidAstroDataError, safelyGetAstroData, and setVfileFrontmatter APIs in favour of isFrontmatterValid

Patch Changes
withastro/astro (@​astrojs/rss)

v4.0.12

Compare Source

Patch Changes
withastro/starlight (@​astrojs/starlight)

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

v0.32.2

Compare Source

Patch Changes

v0.32.1

Compare Source

Patch Changes

v0.32.0

Compare Source

Minor Changes

  • #​2390 f493361 Thanks @​delucis! - Moves route data to Astro.locals instead of passing it down via component props

    ⚠️ Breaking change:
    Previously, all of Starlight’s templating components, including user or plugin overrides, had access to a data object for the current route via Astro.props.
    This data is now available as Astro.locals.starlightRoute instead.

    To update, refactor any component overrides you have:

    • Remove imports of @astrojs/starlight/props, which is now deprecated.
    • Update code that accesses Astro.props to use Astro.locals.starlightRoute instead.
    • Remove any spreading of {...Astro.props} into child components, which is no longer required.

    In the following example, a custom override for Starlight’s LastUpdated component is updated for the new style:

v0.31.1

Compare Source

Patch Changes

v0.31.0

Compare Source

Minor Changes

  • #​2777 88f4214 Thanks @​hippotastic! - Updates astro-expressive-code dependency to the latest version (0.40).

    This includes an update to the latest Shiki version (1.26.1), providing access to all current Shiki themes and syntax highlighting languages, and adding the config options shiki.engine, shiki.bundledLangs, shiki.langAlias and removeUnusedThemes. It also adds new style variants to the optional collapsible sections plugin.

    See the Expressive Code release notes for full details.

  • #​2736 29a885b Thanks @​delucis! - ⚠️ BREAKING CHANGE: The minimum supported version of Astro is now 5.1.5

    Please update Astro and Starlight together:

    npx @&#8203;astrojs/upgrade

  • #​2728 e187383 Thanks @​delucis! - Updates minimum Pagefind dependency to v1.3.0, sets new defaults for Pagefind’s ranking options, and adds support for manually configuring the ranking options

    The new ranking option defaults have been evaluated against Starlight’s own docs to improve the quality of search results. See “Customize Pagefind's result ranking” for more details about how they work.

  • #​157 23bf960 Thanks @​tony-sull! - Adds a print stylesheet to improve the appearance of Starlight docs pages when printed

  • #​2728 e187383 Thanks @​delucis! - Fixes Pagefind logging to respect the Astro log level. When using Astro’s --verbose or --silent CLI flags, these are now respected by Pagefind as well.

Patch Changes

  • #​2792 412effb Thanks @​dhruvkb! - Uses semantic var(--sl-color-hairline) for the page sidebar border instead of var(--sl-color-gray-6). This is visually the same as previously but makes it easier to override the hairline color consistently across a site.

  • #​2736 29a885b Thanks @​delucis! - Updates internal dependencies @astrojs/sitemap and @astrojs/mdx to the latest versions

  • #​2782 d9d415b Thanks @​delucis! - Fixes a documentation link in the JSDoc comment for the StarlightExpressiveCodeOptions type

  • #​2708 442c819 Thanks @​delucis! - Fixes colour contrast correction in code blocks

v0.30.6

Compare Source

Patch Changes

v0.30.5

Compare Source

Patch Changes

v0.30.4

Compare Source

Patch Changes

v0.30.3

Compare Source

Patch Changes

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 added the dependencies Does it update a dependency? label May 26, 2025
@renovate renovate bot requested a review from a team as a code owner May 26, 2025 21:44
@renovate renovate bot added the dependencies Does it update a dependency? label May 26, 2025
@github-project-automation github-project-automation bot moved this to 🪵 Backlog in Documentation May 26, 2025
@netlify Netlify
Copy link

netlify bot commented May 26, 2025 •
edited
Loading

❌ Deploy Preview for tauri-v2 failed.

Name Link
🔨 Latest commit b0cd547
🔍 Latest deploy log https://app.netlify.com/projects/tauri-v2/deploys/684719f5c832c900088a35aa

@renovate renovate bot force-pushed the renovate/astro-and-starlight-packages branch from ac165d7 to 473a41e Compare May 26, 2025 21:55
@FabianLars FabianLars marked this pull request as draft May 26, 2025 21:59
@renovate renovate bot force-pushed the renovate/astro-and-starlight-packages branch 6 times, most recently from d732efd to 0112787 Compare May 29, 2025 16:58
@renovate renovate bot force-pushed the renovate/astro-and-starlight-packages branch 4 times, most recently from 65b472c to 45c327b Compare June 7, 2025 18:38
@renovate renovate bot force-pushed the renovate/astro-and-starlight-packages branch from 45c327b to b0cd547 Compare June 9, 2025 17:29
@socket-security Socket Security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updatedshiki@​3.4.2 ⏵ 3.6.01001007599 +2100
Updatedtypedoc-plugin-markdown@​4.2.10 ⏵ 4.6.4100 +11007892100
Updated@​types/​node@​22.15.21 ⏵ 22.15.30100 +110080 +196100
Updated@​astrojs/​rss@​4.0.11 ⏵ 4.0.1292 -810010092100
Updatedsass@​1.89.0 ⏵ 1.89.110010010096 -1100

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@vasfvitor vasfvitor

Labels
dependencies Does it update a dependency?
Projects
Documentation
Status: 🪵 Backlog
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@vasfvitor