-
Notifications
You must be signed in to change notification settings - Fork 807
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
Release process #661
Release process #661
Conversation
|
||
Merge the PR, and pull the changes locally (using the commands in the first step). Ensure that `chore: x.y.z release proposal` is the most recent commit. | ||
|
||
## Publish all packages |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this need to be a manual process? Why can we not use lerna publish for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So instead of npm publish
on all the packages, just use lerna publish
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So instead of npm publish on all the packages, just use lerna publish?
I believe that lerna publish from-package
should do the same at that point.
Codecov Report
@@ Coverage Diff @@
## master #661 +/- ##
==========================================
+ Coverage 91.66% 92.67% +1.01%
==========================================
Files 217 228 +11
Lines 10305 10361 +56
Branches 915 933 +18
==========================================
+ Hits 9446 9602 +156
+ Misses 859 759 -100
|
|
||
Merge the PR, and pull the changes locally (using the commands in the first step). Ensure that `chore: x.y.z release proposal` is the most recent commit. | ||
|
||
## Publish all packages |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So instead of npm publish on all the packages, just use lerna publish?
I believe that lerna publish from-package
should do the same at that point.
7c41b08
to
45979d8
Compare
…ry#661) Co-authored-by: William Armiros <54150514+willarmiros@users.noreply.github.com> Co-authored-by: Daniel Dyla <dyladan@users.noreply.github.com>
Which problem is this PR solving?