Regarding triggering releases

[baruchiro]

We are using the semantic-release tool to calculate the next SemVer based on the commit messages.

By default, semantic-release uses Angular Commit Message Conventions.
from semantic-release docs

The point is that semantic-release will create a new release only for a subgroup of the allowed messages (fix|feat|perf|BREAKING CHANES), because there is no reason to publish a new version for ci|build etc'. (see semantic-release/semantic-release#2820 (comment))

Now, to reduce the frequency of a release, we changed the release pipeline to be triggered manually by workflow_dispatch.

Considering all the points above, you can understand that now there is a situation when you trigger a release manually, but it still won't trigger a new release (as you can see here).

The question is if we want to return back to the semantic-release defaults, by triggering it on every commit in the master, and the version will be released only when one of the fix|feat|perf|BREAKING CHANES?
Or do we want to continue with the manual way, and force the semantic-release to trigger the release even if it is only ci|build?
(Or keep it like it now- trigger manually, and no release if no commit with fix|feat|perf|BREAKING CHANES)

[baruchiro]

From @jossef: It is the expected behavior, we will trigger the release manually, and a release will be created only if there is a commit with fix|feat|perf|BREAKING CHANES.