ci(release): defined a github workflow to release with semantic-release#923
Conversation
|
this PR will close the Issue #914 as the fix is merged already but not released yet |
|
if adding me as a maintainer could help with details like this, i'd be willing to help out with basic maintenance tasks like this. i wouldnt be able to dedicate a lot of time due to other OSS project responsibilities (hopefully, my reputation on those projects helps build trust to consider me as a maintainer here), but would like to help unblock vulnerability issues like this. |
|
Adding another vote of support; @jimthedev, please consider @travi's offer! I'm sure plenty of repos (like mine) have got a Critical dependabot security alert because there hasn't been a release for commitizen despite the updates being merged in already. |
|
Just got back home. Wife has covid but will take a look and see if I can help. |
|
Secret added, going to merge this. |
|
🎉 This PR is included in version 4.2.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
@jimthedev Thx |
|
@daiyam thank all of you for your patience. |
|
Thank you and @travi for resolving this! |
6 participants
re-enables the release automation that was lost with the cleanup of the
.travis.ymlin #880. theGITHUB_TOKENis provided automatically by the action and should have access to perform all necessary actions needed for the release. theNPM_PUBLISH_TOKENwould need to be made available as a secret to this action by a project maintainer.this does not replace the verification that happens on Azure Pipelines and only runs on the
masterbranch. it is assumed that changes are only ever merged after passing verification in a PR, so this workflow should be safe to implement independently from the existing verification pipelines.this should unblock #914 and #897 (possibly more)