Question: Support for a custom type?

[hendrickson-tyler]

First of all, I'm immensely grateful for this plugin's existence. Thank you for contributing this!

I was curious if the plugin supports additional types that aren't explicitly mentioned in the conventional commits specification. For example, in addition to the usual feat: and fix: types, I'm interested in using an update: type in my project. Reason being, I want to specifically mention items that have outwardly changed, but don't necessarily constitute a new feature.

I've been playing around with the options, but can't ever get my update: commits to be picked up in the release notes—even when using a custom commit_format regex. This is what my actions look like:

...
analyze_commits(
  commit_format: /^(fix|feat|update)(?:\((.*)\))?(!?)\: (.*)/,
  match: 'v[0-9]*.[0-9]*.[0-9]',
  show_version_path: false,
)
notes = conventional_changelog(
  format: 'plain',
  display_title: false,
  display_links: false,
  sections: {
    feat: 'New Features',
    fix: 'Bug Fixes',
    update: 'Other Updates',
    no_type: 'Changes To Remove'
  },
  ignore_scopes: [
    'android',
    'web',
    'back-end',
    'backend',
    'data',
    'core',
    'deps',
    'deps-dev',
])
...

I've verified that my commit message matches the regex I provided, so I wanted to check to see if this is not supported at the moment?

[swilliams-intellum]

The sections parameter is for defining the wording. You can use the order parameter to define which sections are displayed in which order.

section: ['feat', 'fix', 'update']