-
Notifications
You must be signed in to change notification settings - Fork 61
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
Test publish: latest (v0.2.0) npm packages #1058
Conversation
When running "lerna version" to create release commits, it will change indentation to 4 spaces. Unless we already have the same, it will do the change, which we do not want as part of the release commit. This is a one-off. Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
Oops - there are apparent build issues to investigate - back to draft |
Ah, I think that with this change, we end-up somehow pulling
|
c23c754
to
4bc6018
Compare
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
It's a bit strange, but I still had build issues after publishing a new version of |
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.
Looks good to me. Thanks for doing this release!
Thanks for the review! Fingers crossed :) |
This PR tests the recently added CI publishing infrastructure by attempting to publish v0.2.0 of the 3 npm packages in this repo.
When I ran "yarn version:minor" I noticed that it massaged the
package.json
files andlerna.json
, changing indentation from 2 to 4 and making sure there was a terminating line at the end of the files. To make things cleaner, I added a commit that replicated these changes, before the release commit.