Help to define my release pipeline #3213
Replies: 1 comment
-
I can't see your repo, but Node and NPM are required to perform the work of In fact, semantic release does not need to perform the release, just prepare it and it can call other tools to handle publishing to a registry or repo in GitHub or elsewhere. I use semantic release in Maven projects quite effectively, handing off the deploy and publishing of a release to the Maven Release Plugin in the pipeline. I typically don't use GitHub workflows as I'm on GitLab (and I use To Be Continuous CI/CD templates to handle all of the details), but seeing a need to install semantic-releases dependencies and runtime is not unexpected for the simplest of pipelines. |
Beta Was this translation helpful? Give feedback.
-
I would like to use Semantic Release to track all changes done on a simple project repo. I need to maintain a changelog at the root, and to publish a new release on github each time the main branch is updated.
I tried the default recipe (available here), but this is unclear for me why I would need npm and nodes ?
Why those 3 steps are required, as my only goal is to publish a release in my own repo:
Beta Was this translation helpful? Give feedback.
All reactions