ci: automate changelog and release management #189
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introducing conventional commits for automated changelog and release management.
This change aims to standardize our commit messages, facilitating automated tooling for release processes and changelog generation.
Why?
What's Included:
Changes:
For more on conventional commits, see Conventional Commits Documentation.
Allowed Prefixes:
feat
fix
perf
docs
style
deps
refactor
ci
test
revert
build
chore
translation
security
Major Version Trigger: Use
feat!:
to indicate a breaking change that will trigger a major version release.Minor Version Trigger:: use
feat:
to indicate for SemVer minor version bumpPatch Version Trigger:: use
fix:
to bump patch versionNotes:
After merging this pull request, release-please will create release pull request with changed CHANGELOG.md, ready to be submitted.
Example:
lotyp#4