Automatically publish to npm #84
Merged
Conversation
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
This should activate whenever a new release is tagged.
|
Time Change: +532.75ms (3%) Total Time: 15,681.25ms
ℹ️ View Unchanged
|
MaxDesiatov
reviewed
Sep 26, 2020
| with: | ||
| node-version: 12 | ||
| registry-url: https://registry.npmjs.org/ | ||
| - run: npm ci |
There was a problem hiding this comment.
Same here, wouldn't it require a ci script to be defined?
There was a problem hiding this comment.
npm ci is like npm install but it never modifies package.json.
|
Could you test this script on another test repo? |
|
I've verified it works in my |
|
@MaxDesiatov @j-f1 Could you tell me your npm account name? I'll invite you as owner. |
|
I'm |
kateinoigakukun
approved these changes
Sep 27, 2020
|
I’m |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I copied the code from GitHub’s example.
This should activate whenever a new release is tagged.
@kateinoigakukun needs to upload an npm token to the secrets section of the repo for this to work.
Let’s give this a try for v0.7.1.