chore(deps): drop temporary css-in-js workspace resolutions
Proposed changes (including videos or screenshots)
Removes the root resolutions overrides that pinned @rocket.chat/css-in-js, @rocket.chat/css-supports and @rocket.chat/stylis-logical-props-middleware to their workspaces.
They were added in 2f7f69e2b4d because prerelease bumps (e.g. 0.33.2-rc.0) stopped satisfying fuselage's npm range, so yarn installed a second copy from npm and ui-client's declaration build failed with TS2742. Now that every consumer depends on these packages through workspace:, the overrides no longer change resolution: the only lockfile change is one extra workspace:^ descriptor on the existing css-in-js entry.
This is the cleanup step of the workspace-protocol verification sweep. The rest of the sweep found nothing to change: no npm specifier remains for any migrated design-system package, each resolves to a single workspace copy, and fixWorkspaceVersionsBeforePublish rewrites every workspace: range to a real version for all of them.
Issue(s)
Steps to test or reproduce
yarn install, then confirm everynode_modules/@rocket.chat/{css-in-js,css-supports,stylis-logical-props-middleware}is a symlink topackages/yarn turbo run build --filter=@rocket.chat/ui-client... --force(the build that originally failed)yarn turbo run build --filter='...@rocket.chat/css-in-js' --filter='...@rocket.chat/css-supports' --filter='...@rocket.chat/stylis-logical-props-middleware' --filter='!@rocket.chat/meteor' --forceyarn typecheckinapps/meteor
All pass locally.
Further comments
No changeset: only the root manifest and the lockfile change, and no published package is affected.
🤖 Generated with Claude Code
Summary by CodeRabbit
- Chores
- Updated workspace dependency resolution settings.