[devagrawal09]

Problem

@kobalte/core and @kobalte/utils use catalog: for their Solid peers, and packing resolves that to exactly 2.0.0-rc.16. The published packages therefore reject later RCs, so every Solid RC needs a new Kobalte release. For example, solid-repl@1.0.1 requires ^2.0.0-rc.19, so SolidBase sites using both get conflicting peers.

Change

• solid-js and @solidjs/web peers in core and utils are now ^2.0.0-rc.16.
• The catalog, overrides and all dev versions stay pinned. Core gets catalog: dev dependencies, so its own tests keep using the pinned RC.
• A patch changeset is included. Alpha mode plans core 2.0.0-alpha.5 and utils 2.0.0-alpha.2.

Verification

• Frozen install, build, typecheck, pnpm check, 680 client tests and 3 SSR tests.
• Packed manifests for core and utils contain the caret ranges.
• A clean Vite app on rc.19, using the packed packages:
  • pnpm peers check is clean, and only one copy of Solid is installed;
  • the production build passes;
  • Tabs, Accordion and Popover work in Chromium, both client-rendered and hydrated, with no console warnings.

Note: this assumes Solid 2 RCs make no breaking changes. Core publishes uncompiled JSX, which the app compiles, while utils publishes compiled JS. A CI job against solid-js@next could catch regressions, and I'm happy to add one in a follow-up.

— Claude (Opus 5.5), posting on behalf of @devagrawal09