Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🚀 Beta Packages PublishedBranch:
✅ Beta packages have been successfully published to NPM! Install beta version: pnpm add @kubit-ui-web/react-components@2.0.0-beta.72
pnpm add @kubit-ui-web/design-system@2.0.0-beta.32 |
🔍 PR Validation Report (Monorepo)Status: ❌ FAILED 📦 Affected Packages
✅ Validation Results
🎯 Next StepsPlease fix the failing checks before this PR can be merged. |
🚀 Beta Packages PublishedBranch:
✅ Beta packages have been successfully published to NPM! Install beta version: pnpm add @kubit-ui-web/react-components@2.0.0-beta.73
pnpm add @kubit-ui-web/design-system@2.0.0-beta.33 |
🔍 PR Validation Report (Monorepo)Status: ❌ FAILED 📦 Affected Packages
✅ Validation Results
🎯 Next StepsPlease fix the failing checks before this PR can be merged. |
* chore: migrate from pnpm to yarn berry - Update packageManager to yarn@4.9.1 in all package.json files - Add workspaces field to root package.json (replaces pnpm-workspace.yaml) - Rename root package to @kubit-ui-web/monorepo to avoid workspace name conflict - Set root package as private: true - Replace all pnpm script references with yarn equivalents - Create .yarnrc.yml with nodeLinker: node-modules - Update .gitignore for Yarn Berry artifacts - Migrate all 5 GitHub workflows to use Corepack + Yarn caching - Update README.md and CONTRIBUTING.md documentation - Remove pnpm-lock.yaml and pnpm-workspace.yaml - Add yarn.lock * chore: optimize yarn berry monorepo configuration - Fix vercel.json: still had pnpm commands (build, dev, install) - Replace npx with yarn exec in design-system scripts (bv-build, bernova) - Add enableTelemetry: false to .yarnrc.yml - Add dependenciesMeta to root package.json (migrates pnpm-workspace.yaml ignoredBuiltDependencies for bernova and unrs-resolver) * feat(monorepo): add yarn berry constraints, focus, and foreach support - Create yarn.config.cjs with 5 workspace consistency rules: 1. Shared deps must use same version range across workspaces 2. All sub-workspaces must declare packageManager and engines.node 3. Public packages must have publishConfig 4. Workspace cross-references must use workspace:* protocol 5. No package should depend on itself - Auto-fix 4 version drifts caught by constraints: - @rslib/core: ^0.19.6 → ^0.20.0 (design-system) - @types/node: ^25.3.3 → ^25.5.0 (design-system, storybook) - html-validate: ^10.11.0 → ^10.11.1 (storybook) - Add constraints check to both PR validation workflows + reports - Add convenience scripts: constraints, constraints:fix, focus:*, foreach:clean, info:workspaces - Update README.md Scripts Reference with new commands - Update CONTRIBUTING.md with Constraints and Focused Development docs * fix(design-system): break cyclic dependency with react-components Remove optional peerDependency on @kubit-ui-web/react-components from design-system. Yarn Berry resolves workspace:* peerDeps as hard links in node_modules, creating a bidirectional cycle that Turbo 2.x rejects: components → design-system (devDependency) design-system → components (peerDependency, optional) The peerDep was already optional: true, so design-system functions without it. Consumers install both packages per README instructions. * fix(tsconfig): add root node_modules/@types to typeRoots for Yarn Berry hoisting Yarn Berry hoists all dependencies to the root node_modules/. The typeRoots in sub-package tsconfigs only referenced their own node_modules/@types which is empty after hoisting, causing TS2688: Cannot find type definition file for 'node'. Add ../../node_modules/@types to typeRoots in both components and design-system tsconfigs. * fix: resolve TS2688 and recursive turbo invocations under Yarn Berry - Add ../../node_modules to typeRoots in components and design-system tsconfigs. Scoped type packages like @testing-library/jest-dom are not under @types/ so they need the full root node_modules path, not just ../../node_modules/@types. - Remove //#build root task from turbo.json. With Yarn Berry the root package IS a workspace, so Turbo tried to execute the root build script (which calls turbo run build) as a pipeline task, creating infinite recursion. Without //#build, Turbo only runs build in workspace packages and the root script acts as a convenience wrapper. * chore: switch .yarnrc.yml to public npm registry Open source repo should use the public registry (registry.npmjs.org) in the committed config. Developers with JFrog access can override locally via skip-worktree. * fix(vercel): pin Node range and enable Corepack for Yarn Berry - engines.node: '>=22.0.0' → '>=22.0.0 <25.0.0' to prevent Vercel from auto-upgrading to Node 24.x - installCommand: prepend 'corepack enable' so Vercel activates Yarn Berry (4.9.1) from packageManager field instead of falling back to Yarn Classic 1.22.19 * fix(vercel): pin Node range and enable Corepack for Yarn Berry - engines.node: '>=22.0.0' → '>=22.0.0 <25.0.0' to prevent Vercel from auto-upgrading to Node 24.x - installCommand: prepend 'corepack enable' so Vercel activates Yarn Berry (4.9.1) from packageManager field instead of falling back to Yarn Classic 1.22.19
🔍 PR Validation Report (Monorepo)Status: ❌ FAILED 📦 Affected Packages
✅ Validation Results
🎯 Next StepsPlease fix the failing checks before this PR can be merged. |
- Create .env.example with placeholder URLs showing how to configure a private npm registry via YARN_NPM_REGISTRY_SERVER env var - Add 'Private Registry' section to CONTRIBUTING.md explaining the mechanism without exposing any real corporate URLs - No .yarnrc.yml modification needed — env vars take precedence
🔍 PR Validation Report (Monorepo)Status: ❌ FAILED 📦 Affected Packages
✅ Validation Results
🎯 Next StepsPlease fix the failing checks before this PR can be merged. |
…UB_OUTPUT Multi-line commit messages (with body/bullet points) broke the release workflows because 'echo "message=$COMMIT_MSG"' passes each line as a separate file command. Lines starting with '- ' trigger 'Invalid format' errors in GitHub Actions. Fix: use heredoc syntax (message<<EOF / EOF) which safely handles multi-line values in $GITHUB_OUTPUT.
🚀 Beta Packages PublishedBranch:
✅ Beta packages have been successfully published to NPM! Install beta version: yarn add @kubit-ui-web/react-components@2.0.0-beta.74
yarn add @kubit-ui-web/design-system@2.0.0-beta.34 |
🔍 PR Validation Report (Monorepo)Status: ❌ FAILED 📦 Affected Packages
✅ Validation Results
🎯 Next StepsPlease fix the failing checks before this PR can be merged. |
🔍 PR Validation Report (Monorepo)Status: ❌ FAILED 📦 Affected Packages
✅ Validation Results
🎯 Next StepsPlease fix the failing checks before this PR can be merged. |
🔍 PR Validation Report (Monorepo)Status: ❌ FAILED 📦 Affected Packages
✅ Validation Results
🎯 Next StepsPlease fix the failing checks before this PR can be merged. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.