-
Notifications
You must be signed in to change notification settings - Fork 7
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
Publish package to npm #5
Projects
Comments
LaChope
added a commit
that referenced
this issue
Mar 29, 2022
Closed
LaChope
added a commit
that referenced
this issue
Apr 7, 2022
LaChope
added a commit
that referenced
this issue
Apr 7, 2022
LaChope
added a commit
that referenced
this issue
Apr 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Moscow method:
We want to have 2 types of deployments:
releases (major, minor, patch)
pre-releases
Solution of RQ1.*:
Solution for RQ2.*:
Related links:
Here is example of the workflow: https://www.eliostruyf.com/conditional-publish-packages-npm-github-actions/
Here is example of naming convention: https://node.dev/post/an-open-source-maintainers-guide-to-publishing-npm-packages
Guide to set up npm tokens: https://hackernoon.com/publish-npm-packages-using-github-actions-a-how-to-guide-q31c34fg
Semantic versioning -- https://docs.npmjs.com/about-semantic-versioning
The text was updated successfully, but these errors were encountered: