-
Notifications
You must be signed in to change notification settings - Fork 1
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
add github actions to publish package to npm & gpr #9
Conversation
another thing is for org packages on npm and gpr, the package name tends to be https://docs.npmjs.com/creating-and-publishing-an-organization-scoped-package I haven't included this part in this PR but I can in another one. |
If I understand this properly, you're saying "most" packages would be called If that's correct, let's go a head and make that change now. If that's not correct, can you please further explain? |
@tjayrush yup, your understanding is correct. So I will add the change to this repo. |
@tjayrush done. Package renamed to |
I merged your first PR. Thanks for that. I think it caused a few conflicts. Can you please correct them? I'll merge this one when you do. Sorry if I did something wrong. |
This is excellent. Thanks so much. |
Action only runs when a tag is pushed && branch is
main
.Action has 4 jobs:
dist
folder,dist
and publish to npm registry,dist
and publish to GitHub Package Registry,So release process becomes
yarn release
which will triggerrelease
script frompackage.json
then prompt you to select new version (see example). Once version is selected, the version inpackage.json
gets updated, git tags created and pushed. New tags being pushed will trigger CI.Also the above has to be done while in main otherwise CI won't run. So on code updates you would push those updates to whatever branch, merge to main, then run
yarn release
.