@formatter:off
- All notable changes to this project will be documented in this file.
- The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- This template is based on Conventional Commits.
- Changelogs are for humans, not machines.
- There should be an entry for every single version.
- The same types of changes should be grouped.
- Versions and sections should be linkable.
- The latest version comes first.
- The release date of each version is displayed.
- Mention whether you follow Semantic Versioning.
Addedfor new features.Changedfor changes in existing functionality.Deprecatedfor soon-to-be removed features.Removedfor now removed features.Fixedfor any bug fixes.Securityin case of vulnerabilities.Performancefor improvements in performance.Stylefor changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)Docsfor documentation only changesBuildfor changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
A specification for adding human and machine readable meaning to commit messages.
feata new featurefixa bug fixdocsdocumentation only changesstylechanges that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)refactora code change that neither fixes a bug nor adds a featureperfa code change that improves performancetestadding missing tests or correcting existing testsbuildchanges that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)choreother changes- BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.
@formatter:off
- None
- None
- None
- None
- None