-
Notifications
You must be signed in to change notification settings - Fork 39
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
How to release/publish updated versions #28
Comments
You could add CI for publishing - but you'd have to configure smth like semantic-release and be careful with it as it would be automated Personally I prefer manual releases (but u can chose whatever you like). I've tried to add u as maintainer on npm (so u should be able to publish a new release), but not sure if it has worked because their UI is clunky. Just try to do it and if it won't work I'll contact npm to solve this. Usually I add some release scripts like this: "release:patch": "npm version patch && npm publish && git push --follow-tags",
"release:minor": "npm version minor && npm publish && git push --follow-tags",
"release:major": "npm version major && npm publish && git push --follow-tags", You might want to do a trial run first with smth like: npm version preminor && npm publish --tag beta to see if it works for u. Remember that you have to be logged in with ur npm account. |
@Andarist I do not think it worked, I am not listed as a collaborator here |
Ok, it seems that npm's UI is broken and it allowed me to add you as maintainer but actually the system didnt allow it. I've added u to our npm organization and then it clicked. Please try again, should be OK now |
Hi @Andarist
I made a few changes, how can I publish the updated package? Should we add CI to make this easier?
The text was updated successfully, but these errors were encountered: