fix: use root-level verify in publish workflow#72
Merged
Conversation
Per-package `vitest run` fails because the root vitest.config.ts include pattern is relative to cwd, not config location. Run full verify from root instead of per-package in the publish pipeline.
🔍 Pull Request Validation Results
Overall: ✅ All checks passed! ⏰ Generated at: |
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
1 participant
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.
Summary
npm run verifyper-package (working-directory: packages/*), butvitest runuses rootvitest.config.tswith include patternpackages/*/src/**/*.test.ts— relative to cwd, not config locationpackages/platform/, vitest finds no test files and exits with code 1npm run verifyonce from root instead of per-package matrixTest plan
npm run verifypasses locally