Skip to content

Comments

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

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-packages
Open

fix(deps): update npm-packages [skip ci]#37
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-packages

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@11ty/eleventy-fetch ^5.1.0 → ^5.1.1 age adoption passing confidence
@astrojs/starlight (source) ^0.35.2 → ^0.37.6 age adoption passing confidence
@fontsource-variable/jetbrains-mono (source) ^5.2.6 → ^5.2.8 age adoption passing confidence
@zachleat/table-saw ^1.0.6 → ^1.0.7 age adoption passing confidence
astro (source) ^5.13.7 → ^5.17.3 age adoption passing confidence
prettier (source) 3.7.4 → 3.8.1 age adoption passing confidence
sharp (source, changelog) ^0.34.3 → ^0.34.5 age adoption passing confidence
starlight-contributor-list (source) ^0.3.0 → ^0.3.2 age adoption passing confidence
starlight-cooler-credit (source) ^0.4.0 → ^0.5.0 age adoption passing confidence
starlight-image-zoom (source) ^0.13.0 → ^0.13.2 age adoption passing confidence
starlight-links-validator (source) ^0.17.2 → ^0.19.2 age adoption passing confidence
starlight-sidebar-topics (source) ^0.6.0 → ^0.6.2 age adoption passing confidence
starlight-sidebar-topics-dropdown (source) ^0.5.1 → ^0.5.4 age adoption passing confidence
starlight-theme-rapide (source) ^0.5.1 → ^0.5.2 age adoption passing confidence
starlight-view-modes (source) ^0.11.0 → ^0.12.0 age adoption passing confidence

Release Notes

withastro/starlight (@​astrojs/starlight)

v0.37.6

Compare Source

Patch Changes

v0.37.5

Compare Source

Patch Changes

v0.37.4

Compare Source

Patch Changes

  • #​3534 703fab0 Thanks @​HiDeoo! - Fixes support for running builds when npx is unavailable.

    Previously, Starlight would spawn a process to run the Pagefind search indexing binary using npx. On platforms where npx isn’t available, this could cause issues. Starlight now runs Pagefind using its Node.js API to avoid a separate process. As a side effect, you may notice that logging during builds is now less verbose.

  • #​3656 a0e6368 Thanks @​delucis! - Fixes several edge cases in highlighting the current page heading in Starlight’s table of contents

  • #​3663 00cbf00 Thanks @​lines-of-codes! - Adds Thai language support

  • #​3658 ac79329 Thanks @​delucis! - Avoids adding redundant aria-current="false" attributes to sidebar entries

  • #​3382 db295c2 Thanks @​trueberryless! - Fixes an issue where the mobile table of contents is unable to find the first heading when a page has a tall banner.

v0.37.3

Compare Source

Patch Changes

v0.37.2

Compare Source

Patch Changes

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

v5.17.3

Compare Source

Patch Changes

v5.17.2

Compare Source

Patch Changes
  • c13b536 Thanks @​matthewp! - Improves Host header handling for SSR deployments behind proxies

v5.17.1

Compare Source

Patch Changes

  • #​15334 d715f1f Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

    Removes the getFontBuffer() helper function exported from astro:assets when using the experimental Fonts API

    This experimental feature introduced in v15.6.13 ended up causing significant memory usage during build. This feature has been removed and will be reintroduced after further exploration and testing.

    If you were relying on this function, you can replicate the previous behavior manually:

    • On prerendered routes, read the file using node:fs
    • On server rendered routes, fetch files using URLs from fontData and context.url

v5.17.0

Compare Source

Minor Changes

  • #​14932 b19d816 Thanks @​patrickarlt! - Adds support for returning a Promise from the parser() option of the file() loader

    This enables you to run asynchronous code such as fetching remote data or using async parsers when loading files with the Content Layer API.

    For example:

    import { defineCollection } from 'astro:content';
import { file } from 'astro/loaders';

const blog = defineCollection({
  loader: file('src/data/blog.json', {
    parser: async (text) => {
      const data = JSON.parse(text);

      // Perform async operations like fetching additional data
      const enrichedData = await fetch(`https://api.example.com/enrich`, {
        method: 'POST',
        body: JSON.stringify(data),
      }).then((res) => res.json());

      return enrichedData;
    },
  }),
});

export const collections = { blog };

    See the parser() reference documentation for more information.

  • #​15171 f220726 Thanks @​mark-ignacio! - Adds a new, optional kernel configuration option to select a resize algorithm in the Sharp image service

    By default, Sharp resizes images with the lanczos3 kernel. This new config option allows you to set the default resizing algorithm to any resizing option supported by Sharp (e.g. linear, mks2021).

    Kernel selection can produce quite noticeable differences depending on various characteristics of the source image - especially drawn art - so changing the kernel gives you more control over the appearance of images on your site:

    export default defineConfig({
  image: {
    service: {
      entrypoint: 'astro/assets/services/sharp',
      config: {
        kernel: "mks2021"
      }
  }
})

    This selection will apply to all images on your site, and is not yet configurable on a per-image basis. For more information, see Sharps documentation on resizing images.

  • #​15063 08e0fd7 Thanks @​jmortlock! - Adds a new partitioned option when setting a cookie to allow creating partitioned cookies.

    Partitioned cookies can only be read within the context of the top-level site on which they were set. This allows cross-site tracking to be blocked, while still enabling legitimate uses of third-party cookies.

    You can create a partitioned cookie by passing partitioned: true when setting a cookie. Note that partitioned cookies must also be set with secure: true:

    Astro.cookies.set('my-cookie', 'value', {
  partitioned: true,
  secure: true,
});

    For more information, see the AstroCookieSetOptions API reference.

  • #​15022 f1fce0e Thanks @​ascorbic! - Adds a new retainBody option to the glob() loader to allow reducing the size of the data store.

    Currently, the glob() loader stores the raw body of each content file in the entry, in addition to the rendered HTML.

    The retainBody option defaults to true, but you can set it to false to prevent the raw body of content files from being stored in the data store. This significantly reduces the deployed size of the data store and helps avoid hitting size limits for sites with very large collections.

    The rendered body will still be available in the entry.rendered.html property for markdown files, and the entry.filePath property will still point to the original file.

    import { defineCollection } from 'astro:content';
import { glob } from 'astro/loaders';

const blog = defineCollection({
  loader: glob({
    pattern: '**/*.md',
    base: './src/content/blog',
    retainBody: false,
  }),
});

    When retainBody is false, entry.body will be undefined instead of containing the raw file contents.

  • #​15153 928529f Thanks @​jcayzac! - Adds a new background property to the <Image /> component.

    This optional property lets you pass a background color to flatten the image with. By default, Sharp uses a black background when flattening an image that is being converted to a format that does not support transparency (e.g. jpeg). Providing a value for background on an <Image /> component, or passing it to the getImage() helper, will flatten images using that color instead.

    This is especially useful when the requested output format doesn't support an alpha channel (e.g. jpeg) and can't support transparent backgrounds.

    ---
import { Image } from 'astro:assets';
---

<Image
  src="/transparent.png"
  alt="A JPEG with a white background!"
  format="jpeg"
  background="#ffffff"
/>

    See more about this new property in the image reference docs

  • #​15015 54f6006 Thanks @​tony! - Adds optional placement config option for the dev toolbar.

    You can now configure the default toolbar position ('bottom-left', 'bottom-center', or 'bottom-right') via devToolbar.placement in your Astro config. This option is helpful for sites with UI elements (chat widgets, cookie banners) that are consistently obscured by the toolbar in the dev environment.

    You can set a project default that is consistent across environments (e.g. dev machines, browser instances, team members):

    // astro.config.mjs
export default defineConfig({
  devToolbar: {
    placement: 'bottom-left',
  },
});

    User preferences from the toolbar UI (stored in localStorage) still take priority, so this setting can be overridden in individual situations as necessary.

v5.16.16

Compare Source

Patch Changes

v5.16.15

Compare Source

Patch Changes
  • #​15286 0aafc83 Thanks @​florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local provider

v5.16.14

Compare Source

Patch Changes

  • #​15213 c775fce Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

    Updates how the local provider must be used when using the experimental Fonts API

    Previously, there were 2 kinds of font providers: remote and local.

    Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:

    -import { defineConfig } from "astro/config";
+import { defineConfig, fontProviders } from "astro/config";

export default defineConfig({
    experimental: {
        fonts: [{
            name: "Custom",
            cssVariable: "--font-custom",
-            provider: "local",
+            provider: fontProviders.local(),
+            options: {
            variants: [
                {
                    weight: 400,
                    style: "normal",
                    src: ["./src/assets/fonts/custom-400.woff2"]
                },
                {
                    weight: 700,
                    style: "normal",
                    src: ["./src/assets/fonts/custom-700.woff2"]
                }
                // ...
            ]
+            }
        }]
    }
});

    Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.

    See the experimental Fonts API docs for more information.

  • #​15213 c775fce Thanks @​florian-lefebvre! - Exposes root on FontProvider init() context

    When building a custom FontProvider for the experimental Fonts API, the init() method receives a context. This context now exposes a root URL, useful for resolving local files:

    import type { FontProvider } from "astro";

export function registryFontProvider(): FontProvider {
  return {
    // ...
-    init: async ({ storage }) => {
+    init: async ({ storage, root }) => {
        // ...
    },
  };
}

  • #​15185 edabeaa Thanks @​EricGrill! - Add .vercel to .gitignore when adding the Vercel adapter via astro add vercel

v5.16.13

Compare Source

Patch Changes

  • #​15182 cb60ee1 Thanks @​florian-lefebvre! - Adds a new getFontBuffer() method to retrieve font file buffers when using the experimental Fonts API

    The getFontData() helper function from astro:assets was introduced in 5.14.0 to provide access to font family data for use outside of Astro. One of the goals of this API was to be able to retrieve buffers using URLs.

    However, it turned out to be impactical and even impossible during prerendering.

    Astro now exports a new getFontBuffer() helper function from astro:assets to retrieve font file buffers from URL returned by getFontData(). For example, when using satori to generate OpenGraph images:

    // src/pages/og.png.ts

import type{ APIRoute } from "astro"
-import { getFontData } from "astro:assets"
+import { getFontData, getFontBuffer } from "astro:assets"
import satori from "satori"

export const GET: APIRoute = (context) => {
  const data = getFontData("--font-roboto")

  const svg = await satori(
    <div style={{ color: "black" }}>hello, world</div>,
    {
      width: 600,
      height: 400,
      fonts: [
        {
          name: "Roboto",
-          data: await fetch(new URL(data[0].src[0].url, context.url.origin)).then(res => res.arrayBuffer()),
+          data: await getFontBuffer(data[0].src[0].url),
          weight: 400,
          style: "normal",
        },
      ],
    },
  )

  // ...
}

    See the experimental Fonts API documentation for more information.

v5.16.12

Compare Source

Patch Changes

  • #​15175 47ae148 Thanks @​florian-lefebvre! - Allows experimental Font providers to specify family options

    Previously, an Astro FontProvider could only accept options at the provider level when called. That could result in weird data structures for family-specific options.

    Astro FontProviders can now declare family-specific options, by specifying a generic:

    // font-provider.ts
import type { FontProvider } from "astro";
import { retrieveFonts, type Fonts } from "./utils.js",

interface Config {
  token: string;
}

+interface FamilyOptions {
+    minimal?: boolean;
+}

-export function registryFontProvider(config: Config): FontProvider {
+export function registryFontProvider(config: Config): FontProvider<FamilyOptions> {
  let data: Fonts = {}

  return {
    name: "registry",
    config,
    init: async () => {
      data = await retrieveFonts(token);
    },
    listFonts: () => {
      return Object.keys(data);
    },
-    resolveFont: ({ familyName, ...rest }) => {
+    // options is typed as FamilyOptions
+    resolveFont: ({ familyName, options, ...rest }) => {
      const fonts = data[familyName];
      if (fonts) {
        return { fonts };
      }
      return undefined;
    },
  };
}

    Once the font provider is registered in the Astro config, types are automatically inferred:

    // astro.config.ts
import { defineConfig } from "astro/config";
import { registryFontProvider } from "./font-provider";

export default defineConfig({
    experimental: {
        fonts: [{
            provider: registryFontProvider({
              token: "..."
            }),
            name: "Custom",
            cssVariable: "--font-custom",
+            options: {
+                minimal: true
+            }
        }]
    }
});

  • #​15175 47ae148 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

    Updates how options are passed to the Google and Google Icons font providers when using the experimental Fonts API

    Previously, the Google and Google Icons font providers accepted options that were specific to given font families.

    These options must now be set using the options property instead. For example using the Google provider:

    import { defineConfig, fontProviders } from "astro/config";

export default defineConfig({
    experimental: {
        fonts: [{
            name: 'Inter',
            cssVariable: '--astro-font-inter',
            weights: ['300 900'],
-            provider: fontProviders.google({
-                experimental: {
-                    variableAxis: {
-                        Inter: { opsz: ['14..32'] }
-                    }
-                }
-            }),
+            provider: fontProviders.google(),
+            options: {
+                experimental: {
+                    variableAxis: { opsz: ['14..32'] }
+                }
+            }
        }]
    }
})

  • #​15200 c0595b3 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

    Removes getFontData() exported from astro:assets with fontData when using the experimental Fonts API

    Accessing font data can be useful for advanced use cases, such as generating meta tags or Open Graph images. Before, we exposed a getFontData() helper function to retrieve the font data for a given cssVariable. That was however limiting for programmatic usages that need to access all font data.

    The getFontData() helper function is removed and replaced by a new fontData object:

    -import { getFontData } from "astro:assets";
-const data = getFontData("--font-roboto")

+import { fontData } from "astro:assets";
+const data = fontData["--font-roboto"]

    We may reintroduce getFontData() later on for a more friendly DX, based on your feedback.

  • #​15254 8d84b30 Thanks @​lamalex! - Fixes CSS assetsPrefix with remote URLs incorrectly prepending a forward slash

    When using build.assetsPrefix with a remote URL (e.g., https://cdn.example.com) for CSS assets, the generated <link> elements were incorrectly getting a / prepended to the full URL, resulting in invalid URLs like /https://cdn.example.com/assets/style.css.

    This fix checks if the stylesheet link is a remote URL before prepending the forward slash.

  • #​15178 731f52d Thanks @​kedarvartak! - Fixes an issue where stopping the dev server with q+enter incorrectly created a dist folder and copied font files when using the experimental Fonts API

  • #​15230 3da6272 Thanks @​rahuld109! - Fixes greedy regex in error message markdown rendering that caused link syntax examples to capture extra characters

  • #​15253 2a6315a Thanks @​matthewp! - Fixes hydration for React components nested inside HTML elements in MDX files

  • #​15227 9a609f4 Thanks @​matthewp! - Fixes styles not being included for conditionally rendered Svelte 5 components in production builds

  • #​14607 ee52160 Thanks @​simensfo! - Reintroduces css deduplication for hydrated client components. Ensures assets already added to a client chunk are not flagged as orphaned

v5.16.11

Compare Source

Patch Changes

v5.16.10

Compare Source

Patch Changes

  • 2fa19c4 - Improved error handling in the rendering phase

    Added defensive validation in App.render() and #renderError() to provide a descriptive error message when a route module doesn't have a valid page function.

  • #​15199 d8e64ef Thanks @​ArmandPhilippot! - Fixes the links to Astro Docs so that they match the current docs structure.

  • #​15169 b803d8b Thanks @​rururux! - fix: fix image 500 error when moving dist directory in standalone Node

  • #​14622 9b35c62 Thanks @​aprici7y! - Fixes CSS url() references to public assets returning 404 in dev mode when base path is configured

  • #​15219 43df4ce Thanks @​matthewp! - Upgrades the diff package to v8

v5.16.9

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.

@changeset-bot
Copy link

changeset-bot bot commented Jan 8, 2026 •
edited
Loading

⚠️ No Changeset found

Latest commit: 23f1843

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 8, 2026 •
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.

  • 🔍 Trigger a full review

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

@github-actions github-actions bot added the 📦 package Updates in package structure or package.json label Jan 8, 2026
@renovate renovate bot force-pushed the renovate/npm-packages branch 5 times, most recently from aa67c03 to 3bfaa26 Compare January 15, 2026 01:50
@renovate renovate bot force-pushed the renovate/npm-packages branch 7 times, most recently from a5bc4f6 to cef76be Compare January 22, 2026 09:34
@renovate renovate bot force-pushed the renovate/npm-packages branch 7 times, most recently from f3238f6 to 05db75c Compare January 29, 2026 17:31
@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from 75623e9 to d3a131a Compare February 2, 2026 21:14
@renovate renovate bot force-pushed the renovate/npm-packages branch 3 times, most recently from cea41cd to 1107870 Compare February 17, 2026 15:34
@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from 5fed6e7 to 03d862c Compare February 19, 2026 14:02
@renovate renovate bot force-pushed the renovate/npm-packages branch from 03d862c to 23f1843 Compare February 19, 2026 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

📦 package Updates in package structure or package.json

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants