-
-
Notifications
You must be signed in to change notification settings - Fork 57
Automatically publish to npm #84
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
Conversation
This should activate whenever a new release is tagged.
|
Time Change: +532.75ms (3%) Total Time: 15,681.25ms
i️ View Unchanged
|
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.
Same here, wouldn't it require a ci script to be defined?
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.
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 gatsby-remark-codemirror package. Good to go, you just need to add the npm_token secret, and make sure your npm OTP is authorization-only if you have it enabled.
@MaxDesiatov @j-f1 Could you tell me your npm account name? I'll invite you as owner.
I'm maxd on npm 🙂
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.
👍
I’m j-f on npm.
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.