-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: fix ci.yml canary releases to use nx, not lerna #8962
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: fix ci.yml canary releases to use nx, not lerna #8962
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8962 +/- ##
==========================================
+ Coverage 87.40% 88.05% +0.64%
==========================================
Files 257 407 +150
Lines 12525 14103 +1578
Branches 3928 4126 +198
==========================================
+ Hits 10948 12418 +1470
- Misses 1303 1381 +78
- Partials 274 304 +30
Flags with carried forward coverage won't be shown. Click here to find out more. |
4858afd
into
typescript-eslint:main
PR Checklist
Overview
I'm ... not sure which command we should use here 😬 is it ...✅nx release
?Partially overlaps #8913.
💖