release-notes-generator | generate markdown release notes that comprise the list | DevOps library

If anyone finds this useful: we need to config "@semantic-release/release-notes-generator" for considering other keywords besides feat and fix including these dicts:

1.In GitLab you have to explicitly set the script to push to Git. For this you need to create a token and pass it to your CI via env variable.

In example, see how we do it in our integration project via setting GIT_PUSH_TOKEN - here: https://gitlab.com/taleodor/sample-helm-cd

and the actual ci yaml code here: https://gitlab.com/taleodor/sample-helm-cd/-/blob/master/.gitlab-ci.yml (lines 25-30).

2.Yes, direct push on version bump is common.

It's because grep -E is working with extended regular expression which doesn't support \d. So you have two solutions:

• use grep -P to use Perl regular expression and work with \d
• use grep -E but change your regex as [[:digit:]]+\.[[:digit:]]+\.[[:digit:]]+ or [0-9]+\.[0-9]+\.[0-9]+

I resolved the problem myself. I suspected that the problem is due to some version incompatibities of semantic-release plugins that I was using with the library. I tried different versions of semantic-release but I had no success.

Finally, I checked the Nodejs version (node --version) of my CircleCI executor which was a machine executor (image: ubuntu-1604:201903-01). I found that the node version in that executor was so old (v6.x.x). I needed that machine executor to run my tests as I had to mock some aws features through other docker images running on the machine. However, could change the executor to a Nodejs docker executor for the release step. So, I did this and problem was resolved.

For example, I added something like the following at the beginning of my CircleCI config:

I fixed it by installing a previous version of npm-scripts Try using this:

You will have to implement your own conventional-changelog preset in order to handle those new commit type.

For example the default angular preset handles only certain commit types: https://github.com/conventional-changelog/conventional-changelog/blob/e865af4df8d06795cebc7af09364ade19119e089/packages/conventional-changelog-angular/writer-opts.js#L36

But I'm wondering how to customize it to fit our workflow: * no dev branch, just a master and feature/fix/chore branches. * latest release (github with relevant git tag) correspond to version pushed to production. * Draft release correspond to version pushed to staging.

It only analyze the commit on the branch that you configure (by default master). It doesn't matter how the commit get there, you can merge them in any branch you want before they reach master. When they get to master and semantic-release run it will analyze the commits on master and make a release if necessary.

semantic-release doesn't support draft/pre-release yet (See https://github.com/semantic-release/semantic-release/issues/563).

I recently installed the semantic pull request github app

What you are referring to? There is no semantic-release GitHub app at that point, even though it's planned to have one at some point (https://github.com/semantic-release/semantic-release/issues/585).

but I'm unclear about how to use release-notes-generator on its own, or whether it handles the github draft release mode

release-notes-generator is responsible for generating the release note and doesn't interact with GitHub. The @semantic-release/github is responsible for creating the release on GitHub.

I've finally made it work.

The problem was that npm i @semantic-release/git --save-dev would install the git plugin at version 3.0.1, and I was reading the API for for version 4.0.0.

To solve it, I did