Skip to content

chore(deps): update pnpm workspace dependencies - #106

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/pnpm-workspace-dependencies
Open

chore(deps): update pnpm workspace dependencies#106
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/pnpm-workspace-dependencies

Conversation

@renovate

@renovate renovate Bot commented Mar 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/check (source) ^0.9.6 → ^0.9.10 age confidence
@astrojs/starlight (source) ^0.37.6 → ^0.42.0 age confidence
@vue/language-core (source) ^3.2.5 → ^3.3.11 age confidence
astro (source) ^5.18.0 → ^5.18.2 age confidence
astro-expressive-code (source) ^0.41.7 → ^0.44.2 age confidence
rehype-expressive-code (source) ^0.41.7 → ^0.44.2 age confidence
twoslash-eslint (source) ^0.3.6 → ^0.3.9 age confidence
twoslash-protocol (source) ^0.3.6 → ^0.3.9 age confidence
vue (source) ^3.5.29 → ^3.5.42 age confidence

Release Notes

withastro/astro (@​astrojs/check)

v0.9.10

Compare Source

Patch Changes

v0.9.9

Compare Source

Patch Changes

v0.9.8

Compare Source

Patch Changes

v0.9.7

Compare Source

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

v0.42.0

Compare Source

Minor Changes

  • #​3572 292fb17 Thanks @​HiDeoo! - Distributes package as JavaScript files with dedicated type declaration files instead of TypeScript source files.

  • #​4121 2623ae6 Thanks @​delucis! - Simplifies markup for Starlight’s mobile menu toggle

    ⚠️ Potentially breaking change: If you use a theme plugin, custom styles, or component overrides targeting the MobileMenuToggle button or PageFrame components, you may need to adjust these for the new markup. The button is no longer wrapped in a <starlight-menu-button> custom element and no longer uses the aria-expanded attribute. Instead, you can use the .sl-menu-button class name to target the button and the :popover-open pseudo-class to style the menu open state specifically.

    In the following example, custom styles for the menu button are updated for the new approach:

    - starlight-menu-button button {
+ .sl-menu-button {
  color: var(--sl-color-text);
}

- starlight-menu-button[aria-expanded='true'] button {
+ .sl-menu-button:has(~ :popover-open) {
  color: var(--sl-color-text-accent-high);
}

    See MobileMenuToggle.astro and PageFrame.astro on GitHub for the full source code of the updated components.

  • #​3572 292fb17 Thanks @​HiDeoo! - Removes the tagline configuration option, which was never used.

    If your configuration included a tagline option, you can safely remove it without any replacement.

  • #​4134 6135f01 Thanks @​HiDeoo! - Updates internal @astrojs/mdx, @astrojs/markdown-satteri, and satteri dependencies.

    ⚠️ BREAKING CHANGE: The following minimum versions are now required:

    • astro v7.2.10 or later
    • @astrojs/markdown-satteri 0.4.0 or later (if you use it)
    • @astrojs/markdown-remark 7.3.0 or later (if you use it)

    Please update Starlight and Astro together:

    npx @astrojs/upgrade

  • #​4121 2623ae6 Thanks @​delucis! - Refactors Starlight’s mobile menu toggle to work when JavaScript fails or is disabled

    ⚠️ BREAKING CHANGE: This release drops official support for Chromium-based browsers prior to version 116 (released August 2023), Safari-based browsers prior to version 17.0 (released September 2023), and Firefox prior to version 125 (released April 2024). You can find a list of currently supported browsers and their versions using this browserslist query.

    This change also removes the data-mobile-menu-expanded attribute, which was previously added to <body> while the mobile menu is open. If you have custom code that was depending on this attribute, you will need to update it to use a new selector to check if the mobile menu is open.

    In the following example, a custom background colour for the site header while the menu is open is updated for the new approach:

    - [data-mobile-menu-expanded] header {
+ body:has(sl-sidebar-pane:popover-open) header {
  background-color: var(--sl-color-bg);
}

v0.41.11

Compare Source

Patch Changes

  • #​4167 32a5e29 Thanks @​HiDeoo! - Fixes a layout issue and anchor links appearing for hidden headings, e.g. footnote headings, when markdown.headingLinks is enabled or the <AnchorHeading> component is used.

  • #​4148 cdfafd8 Thanks @​ematipico! - Optimizes sidebar data generation logic to speed up sites with large sidebars

v0.41.10

Compare Source

Patch Changes

v0.41.9

Compare Source

Patch Changes

v0.41.8

Compare Source

Patch Changes

v0.41.7

Compare Source

Patch Changes
  • #​4114 3e486fb Thanks @​delucis! - Fixes processing of code examples in RTL languages when using Astro’s Sätteri Markdown processor

v0.41.6

Compare Source

Patch Changes

v0.41.5

Compare Source

Patch Changes

v0.41.4

Compare Source

Patch Changes

v0.41.3

Compare Source

Patch Changes
  • #​3911 1686ecc Thanks @​timothyjordan! - Keeps keyboard focus inside the mobile menu while it is open, preventing focus moving to hidden interactive elements in page content.

v0.41.2

Compare Source

Patch Changes

  • #​4008 58a3520 Thanks @​FrancoKaddour! - Fixes the table of contents overflowing the right edge of the viewport when a custom --sl-content-width value exceeds available space

  • #​4015 bdbfffc Thanks @​delucis! - Fixes an issue where aside icons were rendered incorrectly in projects where Astro’s MDX integration had optimization disabled

v0.41.1

Compare Source

Patch Changes

v0.41.0

Compare Source

Minor Changes
Upgrade Astro and dependencies

⚠️ BREAKING CHANGE: Astro v6 is no longer supported. Make sure you update Astro and any other official integrations at the same time as updating Starlight:

npx @astrojs/upgrade

Community Starlight plugins and Astro integrations may also need to be manually updated to work with Astro v7. If you encounter any issues, please reach out to the plugin or integration author to see if it is a known issue or if an updated version is being worked on.

⚠️ BREAKING CHANGE: This release drops official support for Chromium-based browsers prior to version 111 (released 07 March 2023) and Safari-based browsers prior to version 16.4 (released 27 March 2023). You can find a list of currently supported browsers and their versions using this browserslist query.

Patch Changes
  • #​3953 a935d33 Thanks @​HiDeoo! - Fixes Starlight Markdown processing being potentially applied to files that should not be processed.

v0.40.0

Compare Source

Minor Changes

  • #​3923 edf2e6b Thanks @​Princesseuh! - Adds support for Astro 6.4 and the new Sätteri Markdown processor.

    It is now possible to opt into using Astro's 6.4 Sätteri Markdown processor by installing the @astrojs/markdown-satteri package and configuring it in your astro.config.mjs file:

    // astro.config.mjs

import { defineConfig } from 'astro/config';
import { satteri } from '@astrojs/markdown-satteri';

export default defineConfig({
  markdown: {
    processor: satteri(),
  },
});

    ⚠️ BREAKING CHANGE: The minimum supported version of Astro is now v6.4.5.

    Please update Starlight and Astro together:

    npx @astrojs/upgrade

    Community Starlight plugins and Astro integrations may also need to be manually updated to work with Sätteri. If you encounter any issues, please reach out to the plugin or integration author to see if it is a known issue or if an updated version is being worked on.

Patch Changes

v0.39.3

Compare Source

Patch Changes

v0.39.2

Compare Source

Patch Changes

v0.39.1

Compare Source

Patch Changes

  • #​3885 010eed1 Thanks @​ArmandPhilippot! - Fixes the version mentioned in an error message related to autogenerated sidebar groups support.

  • #​3887 b3c6990 Thanks @​delucis! - Adds 13 new icons: clock, desktop, mobile-android, window, database, server, code-branch, notes, question, question-circle, analytics, padlock, and solidjs.

v0.39.0

Compare Source

Minor Changes

  • #​3618 dcf6d09 Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: This release changes how autogenerated links work in Starlight’s sidebar configuration.

    If you have sidebar groups using the autogenerate key, you must now wrap that configuration in an items array:

    {
    label: 'My group',
-   autogenerate: { directory: 'some-dir' },
+   items: [{ autogenerate: { directory: 'some-dir' } }],
}

    This change unlocks the possibility to mix autogenerated links and other links in a single group, for example:

    {
  label: 'Mixed group',
  items: [
    'example-page',
    { autogenerate: { directory: 'examples' } },
    { label: 'More examples', link: 'https://example.com' },
  ],
}

    This release also updates the shape of autogenerated sidebar entries in route data. Autogenerated links and groups in Astro.locals.starlightRoute.sidebar now include an autogenerate object with the configured directory value:

    {
  type: 'link',
  label: 'Example',
  href: '/examples/example/',
  isCurrent: false,
  autogenerate: { directory: 'examples' }
}

  • #​3618 dcf6d09 Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: This release changes the default collapsed state of autogenerated sidebar subgroups.

    Autogenerated subgroups no longer inherit the collapsed value from their parent group. They are now expanded by default unless explicitly configured with autogenerate.collapsed.

    If your sidebar configuration relies on a collapsed parent group to also collapse its autogenerated subgroups, update your configuration to set autogenerate.collapsed to true:

    {
  label: 'Reference',
  collapsed: true,
  items: [
-   { autogenerate: { directory: 'reference' } },
+   { autogenerate: { directory: 'reference', collapsed: true } },
  ],
}

  • #​3845 4d755f5 Thanks @​delucis! - Adds a <link rel="alternate" hreflang="x-default" href="..."> tag pointing to the default locale in multilingual sites. The x-default alternate is used as a signal of which language to fall back to if no other is available. Learn more in Google’s SEO localization docs.

  • #​3862 ec70630 Thanks @​itrew! - Makes spacing of items in nested lists more consistent

  • #​3872 417a66c Thanks @​tats-u! - Enables the CSS property text-autospace in Chinese and Japanese documents.

    If you would prefer to disable autospacing in Chinese and Japanese pages, you can add the following custom CSS to your site:

    [lang]:where(:lang(zh, ja)) {
  text-autospace: initial;
}

  • #​3797 9764ebd Thanks @​delucis! - Avoids the risk of layout shift when users expand and collapse sidebar groups

    This release can introduce additional padding to the site sidebar on certain devices to reserve space for scrollbars. You may wish to inspect your site sidebar visually when upgrading.

    If you would prefer to keep the previous styling, you can add the following custom CSS to your site:

    .sidebar-pane {
  scrollbar-gutter: auto;
}

  • #​3858 6672c35 Thanks @​delucis! - Updates i18next, used for Starlight’s localization APIs, from v23 to v26

    There should not be any user-facing changes from this update

v0.38.5

Compare Source

Patch Changes

v0.38.4

Compare Source

Patch Changes

v0.38.3

Compare Source

Patch Changes

v0.38.2

Compare Source

Patch Changes

  • #​3759 f24ce99 Thanks @​MilesChou! - Fixes an issue where monolingual sites using a region-specific locale (e.g., zh-TW) as the default would incorrectly display base language translations (e.g., zh Simplified Chinese) instead of the region-specific ones (e.g., zh-TW Traditional Chinese).

  • #​3768 a4c6c20 Thanks @​delucis! - Improves performance of sidebar generation for sites with very large sidebars

v0.38.1

Compare Source

Patch Changes

v0.38.0

Compare Source

Minor Changes
Upgrade Astro and dependencies

⚠️ BREAKING CHANGE: Astro v5 is no longer supported. Make sure you update Astro and any other official integrations at the same time as updating Starlight:

npx @astrojs/upgrade

Community Starlight plugins and Astro integrations may also need to be manually updated to work with Astro v6. If you encounter any issues, please reach out to the plugin or integration author to see if it is a known issue or if an updated version is being worked on.

Update your collections

⚠️ BREAKING CHANGE: Drops support for content collections backwards compatibility.

In Astro 5.x, projects could delay upgrading to the new Content Layer API introduced for content collections because of some existing automatic backwards compatibility that was not previously behind a flag. This meant that it was possible to upgrade from Astro 4 to Astro 5 without updating your content collections, even if you had not enabled the legacy.collections flag. Projects would continue to build, and no errors or warnings would be displayed.

Astro v6.0 now removes this automatic legacy content collections support, along with the legacy.collections flag.

If you experience content collections errors after updating to v6, check your project for any removed legacy features that may need updating to the Content Layer API. See the Starlight v0.30.0 upgrade guide for detailed instructions on upgrading legacy collections to the new Content Layer API.

If you are unable to make any changes to your collections at this time, including Starlight's default docs and i18n collections, you can enable the legacy.collectionsBackwardsCompat flag to upgrade to v6 without updating your collections. This temporary flag preserves some legacy v4 content collections features, and will allow you to keep your collections in their current state until the legacy flag is no longer supported.

  • #​3704 375edcc Thanks @​florian-lefebvre! - Fixes autocomplete for components exported from @astrojs/starlight/components/*

    ⚠️ Potentially breaking change: This change moves some files used in Starlight’s component internals out of the components/ directory. Direct use of these files was not and is not officially supported. If you previously imported TableOfContents/starlight-toc.ts, TableOfContents/TableOfContentsList.astro, Icons.ts, or SidebarPersistState.ts, please review your code when updating.

  • #​3729 3642625 Thanks @​delucis! - Improves Starlight’s default body font stack to better support languages such as Chinese, Japanese, and Korean on Windows.
    For most users there should be no visible change.

    If you would prefer to keep the previous font stack, you can add the following custom CSS to your site:

    :root {
  --sl-font-system: ui-sans-serif, system-ui, 'Segoe UI', Roboto,
    'Helvetica Neue', Arial, 'Noto Sans', sans-serif, 'Apple Color Emoji',
    'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji';
}

  • #​3598 fff38d5 Thanks @​HiDeoo! - Makes hover styles consistent in Starlight’s navigation bar

    Previously, the social icon links and language/theme switchers in Starlight’s navigation bar, dimmed on hover.
    After this change, they now increase in contrast on hover instead.
    This matches hover behavior elsewhere, for example in the sidebar, table of contents, or search button.

    ⚠️ Potentially breaking change: this is a subtle change to the hover style colors.
    If you want to preserve the previous styling, you can add the following custom CSS to your site:

    starlight-theme-select label,
starlight-lang-select label {
  color: var(--sl-color-gray-1);

  &:hover {
    color: var(--sl-color-white);
  }
}

.social-icons a:hover {
  color: var(--sl-color-text-accent);
  opacity: 0.66;
}

v0.37.7

Compare Source

Patch Changes
  • #​3726 8a09b60 Thanks @​delucis! - Fixes an issue using components containing scripts inside Starlight’s steps component in versions of Astro >= 5.16.9
vuejs/language-tools (@​vue/language-core)

v3.3.11

Compare Source

language-core
language-service
component-meta
tsc
vscode

v3.3.10

Compare Source

language-core
  • fix: ignore trailing whitespace after generic parameter commas - Thanks to @​KazariEX!
  • fix: resolve v-for item type over generic sources (#​6141) - Thanks to @​serkodev!
  • fix: do not extract SFC blocks across inline Markdown code (#​6145) - Thanks to @​lazerg!
language-service
  • fix: serialize template data provider access across concurrent requests (#​6154) - Thanks to @​serkodev!
tsc
  • fix: support different extension sets across project references (#​6146) - Thanks to @​lazerg!
typescript-plugin
vscode
  • feat: patch typescript.js via --require to support read-only file systems (#​6149) - Thanks to @​serkodev!
  • fix: isolate custom TypeScript plugin paths between profiles (#​6148) - Thanks to @​serkodev!

v3.3.9

Compare Source

component-meta
language-core
language-service
  • fix: preserve trailing modifiers when completing in the middle of a directive (#​6133) - Thanks to @​lazerg!
  • fix: only replace current directive modifier on completion - Thanks to @​KazariEX!
  • fix: preserve current modifier when filtering completion duplicates - Thanks to @​KazariEX!
workspace
  • feat: migrate build and tests to typescript-native-bridge (#​6129)

v3.3.8

Compare Source

language-core
workspace

v3.3.7

Compare Source

language-core
  • fix: wrap single expression event handlers to avoid ASI after return (#​6115) - Thanks to @​KazariEX!
typescript-plugin
  • fix: filter const globals from template completions

v3.3.6

Compare Source

language-core
  • fix: make generic component internal context inference type-safe across .d.ts boundary (#​6104) - Thanks to @​Holiden!
  • fix: do not treat non-trivial property accesses as compound - Thanks to @​KazariEX!
  • fix: treat semicolon-terminated expressions as compound - Thanks to @​KazariEX!
  • fix: preserve return types for compound event handlers - Thanks to @​KazariEX!
  • fix: use WeakMap to cache inline TS ASTs - Thanks to @​KazariEX!
  • fix: match upstream CSS v-bind parsing behavior - Thanks to @​KazariEX!
  • fix: include setup bindings as potential component names (#​6111) - Thanks to @​KazariEX!
  • perf: reduce boundary code feature allocations - Thanks to @​KazariEX!
  • refactor: centralize code features and deprecate allCodeFeatures - Thanks to @​KazariEX!

v3.3.5

Compare Source

language-core

v3.3.4

Compare Source

language-core
  • fix: only exclude already-set props from inherited attrs when checkRequiredFallthroughAttributes is enabled (#​6088) - Thanks to @​KazariEX!
  • fix: camelize slot props regardless of htmlAttributes option (#​6089) - Thanks to @​KazariEX!
  • fix: detect duplicate event listeners across name formats (#​6094) - Thanks to @​whysopaul!
language-service
typescript-plugin

v3.3.3

Compare Source

vscode
workspace

v3.3.2

Compare Source

language-core
  • feat: preserve literal types for inline v-for sources (#​6067) - Thanks to @​kkesidis!
  • fix: align v-bind shorthand identifier skipping with interpolation - Thanks to @​KazariEX!
vscode
  • feat: transform tsserver content ([#​6062

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • 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 review from a team and Adammatthiesen as code owners March 16, 2026 01:39
@htg-1-studiocms-cloud

htg-1-studiocms-cloud Bot commented Mar 16, 2026 •
edited
Loading

Copy link
Copy Markdown

Dokploy Preview Deployment

Name Status Preview Updated (UTC)
Expressive-Code-Twoslash Docs ❌ Failed Preview URL 2026-03-16T01:49:56.501Z

@changeset-bot

changeset-bot Bot commented Mar 16, 2026 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: ecae955

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@htg-1-studiocms-cloud

htg-1-studiocms-cloud Bot commented Mar 16, 2026 •
edited
Loading

Copy link
Copy Markdown

Dokploy Preview Deployment

Name Status Preview Updated (UTC)
Expressive-Code-Twoslash Docs ❌ Failed Preview URL 2026-03-16T01:50:46.002Z

@htg-1-studiocms-cloud

htg-1-studiocms-cloud Bot commented Mar 16, 2026 •
edited
Loading

Copy link
Copy Markdown

Dokploy Preview Deployment

Name Status Preview Updated (UTC)
Expressive-Code-Twoslash Docs ❌ Failed Preview URL 2026-03-16T01:51:34.632Z

@apollo-git-bot

apollo-git-bot Bot commented Mar 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Allure Report Summary

Name Duration Stats New Flaky Retry Report
@ec-ts/twoslash Tests 29s 928ms Passed tests 29 94 0 0
css-js-gen Tests 27ms Passed tests 37 94 0 0
@ec-ts/vfs Tests 9s 530ms Passed tests 21 94 0 0
@ec-ts/twoslash-vue Tests 6s 303ms Passed tests 6   Failed tests 1 94 0 0

@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 2 times, most recently from 4ba319e to 610db7b Compare March 20, 2026 13:39
@Adammatthiesen Adammatthiesen mentioned this pull request Mar 23, 2026
Open
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch from 610db7b to b99f2b3 Compare March 23, 2026 22:11
@htg-1-studiocms-cloud

htg-1-studiocms-cloud Bot commented Mar 23, 2026 •
edited
Loading

Copy link
Copy Markdown

Dokploy Preview Deployment

Name Status Preview Updated (UTC)
Expressive-Code-Twoslash Docs ❌ Failed Preview URL 2026-03-28T09:58:43.713Z

@pkg-pr-new

pkg-pr-new Bot commented Mar 23, 2026 •
edited
Loading

Copy link
Copy Markdown
css-js-gen

npm i https://pkg.pr.new/css-js-gen@106

expressive-code-twoslash

npm i https://pkg.pr.new/expressive-code-twoslash@106

@ec-ts/twoslash

npm i https://pkg.pr.new/@ec-ts/twoslash@106

@ec-ts/twoslash-vue

npm i https://pkg.pr.new/@ec-ts/twoslash-vue@106

@ec-ts/vfs

npm i https://pkg.pr.new/@ec-ts/vfs@106

commit: ecae955

@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 2 times, most recently from e32950a to 01bd2ce Compare April 1, 2026 17:21
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 4 times, most recently from 5b55897 to 6b59912 Compare April 13, 2026 09:15
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 3 times, most recently from 6dbea98 to a71b953 Compare April 25, 2026 09:08
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 3 times, most recently from 18939cd to de46957 Compare May 1, 2026 14:34
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 3 times, most recently from fa347d1 to f65e419 Compare May 8, 2026 21:14
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 2 times, most recently from 099171d to e48e10d Compare June 16, 2026 11:40
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 4 times, most recently from be21f1f to 3c7ddc8 Compare June 28, 2026 13:45
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 3 times, most recently from 3c46144 to 4dfb7c6 Compare July 6, 2026 23:43
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 4 times, most recently from 6e8ecbb to 88a5050 Compare July 17, 2026 01:05
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 4 times, most recently from 5c349fd to c14e1cf Compare July 25, 2026 17:02
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 4 times, most recently from 551695b to 18840f9 Compare August 3, 2026 21:26
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 4 times, most recently from c93c780 to b44e88c Compare August 14, 2026 17:43
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 2 times, most recently from 4978f6d to 2dd868f Compare August 24, 2026 22:54
@renovate
renovate Bot force-pushed the renovate/pnpm-workspace-dependencies branch 2 times, most recently from 37e615d to 2414935 Compare August 28, 2026 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Adammatthiesen Adammatthiesen Awaiting requested review from Adammatthiesen Adammatthiesen is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants