-
-
Notifications
You must be signed in to change notification settings - Fork 22
infra: CI manages release process #58
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
base: master
Are you sure you want to change the base?
Conversation
4838344 to
531e2c0
Compare
|
This has implemented the review feedback in thlorenz/doctoc#289 |
|
@AndrewSouthpaw / @thlorenz how can we progress this release process automation pr as this library is now ready for a release? |
|
Unfortunately, I don't have admin access to @thlorenz could you add me as a collaborator so I can set this up? |
|
Thanks @AndrewSouthpaw note that the CI pipeline has been defined such that even if the npm upload failed the creation of the github release would still complete. This github release would contain the files which could be uploaded to npm. |
|
@thlorenz could we get some assistance/input from you so that we can do a release and then prepare to release doctoc. |
|
Hey sorry, life was keeping me busy over the last weeks. |
|
No worries, thanks for doing that. |
This introduces github workflow for managing releases. This workflow is triggered when a tag is added to a commit and performs the following:
Required steps by maintainers: