[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant]
Type of Change
Our release process assumes you are using Conventional Commit messages.
The most important prefixes you should have in mind are:
fix: which represents bug fixes and correlates to a SemVer patch.
feat: which represents a new feature, and correlates to a SemVer minor.
feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a major version change.
If you have not included a conventional commit message this can be fixed on merge.
Description
[Please describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves, or any Discourse or StackOverflow discussions that are relevant]
Type of Change
Our release process assumes you are using Conventional Commit messages.
The most important prefixes you should have in mind are:
fix: which represents bug fixes and correlates to a SemVer patch. feat: which represents a new feature, and correlates to a SemVer minor. feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a major version change.
If you have not included a conventional commit message this can be fixed on merge.
Check List