@aaltat, thank you for your feedback. This feature is available through user configuration but is not set up by default (yet). You should add a list of regular expressions to the setting semantic_release.changelog.exclude_commit_patterns for the commits you do not want to be included in the changelog.

Dependabot's commits are fairly standardized which make this relatively easy. You can look at this project's configuration as I have already defined numerous regular expressions to filter out non-user relevant commits. It works quite well for the conventional commit standard.

There is a significant amount of work in progress that will help set better default changelogs in the future but the milestone is not complete yet. Setting better defaults for changelogs to filter out based on commit parser is one effort which would solve this request.

If you want to also clear the additional clutter of the entire commit message (dependabots commit body) then you will want to look into customizing your changelog where you can easily change the output to only include the commit.descriptions.0 rather than the entire commit. This also will be more default in the future (#866) once I can handle squash commits more nicely.

Other thing that comes in my mind is to tell order based on the tags. Backwards incompatible, feat and fix first, then rest. Or is that possible already?

I did not see that I can pass the exclude commit pattern with GitHub action, I need to investigate it more. Thanks for the tip.

Thank you for the good work with the project.

I did not see that I can pass the exclude commit pattern with GitHub action, I need to investigate it more. Thanks for the tip.

Happy to help! And no, it's not quite passed through to the action via the yaml but instead when your project repo is mounted into the PSR container, it will read a project configuration out of your configuration file (pyproject.toml by default, otherwise specify via -c in root options).

order based on the tags... Or is that possible already?

It would only be possible through providing a custom template currently. You can reference #866 for an example of defining the tag order in a macro and then using the list to pick out desired change types in the order you want.

I think I will go with the exclude pattern, at least first. Although custom template is an option if exclude pattern doesn’t work in my case.

Because what I want is actually possible, should we close the issue?

Glad to help and let me know if you have trouble getting the exclusions to work.