Repository navigation
Add error message and exit when there are no versionable packages - #1466
Conversation
🦋 Changeset detectedLatest commit: ee1ff40 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1466 +/- ##
==========================================
+ Coverage 81.02% 81.04% +0.02%
==========================================
Files 54 54
Lines 2213 2221 +8
Branches 654 661 +7
==========================================
+ Hits 1793 1800 +7
- Misses 416 417 +1
Partials 4 4 ☔ View full report in Codecov by Sentry. |
1c04a81 to
7e9886e
Compare
7e9886e to
7ff6f59
Compare
bluwy
left a comment
There was a problem hiding this comment.
I think the flow and fix here looks good. Not sure if others have thoughts on the error logged info.
| error("No versionable packages found"); | ||
| error('- Ensure the packages to version are not in the "ignore" config'); | ||
| error('- Ensure that relevant package.json files have the "version" field'); | ||
| throw new ExitError(1); |
There was a problem hiding this comment.
note for myself: this is nicely handled here:
changesets/packages/cli/src/index.ts
Lines 105 to 107 in 7ccb22e
so 👍
Close #1170
fix #841
I have added an informative message in the scenario where no versionable packages are found.
This should cover also the error reported in the issue linked above (public packages without
versionfield in package).