Set up versioning by using git tags or files.
10K+
Increment a version number as per Semantic Versioning 2.0.0 specifications
If you don't provide the current version, Git tags will be checked to see if they contain a version string as defined at https://semver.org/
To determine the type of change, the Conventional Commits rules are used (you can override this with a cli argument):
The commit message should be structured as follows:
[optional scope]:
[optional body]
[optional footer(s)]
The commit contains the following structural elements, to communicate intent to the consumers of your library:
- fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in semantic versioning).
- feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in semantic versioning).
- 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.
- types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.
- footers other than BREAKING CHANGE: may be provided and follow a convention similar to git trailer format.
A BREAKING CHANGE increments the major number, and resets the feature and patch number to zero (e.g. 4.0.7 -> 5.0.0)
A feature increments the minor number, and resets the patch number to zero (e.g. 4.0.7 -> 4.1.0)
All other types increment the patch number (e.g. 4.0.7 -> 4.0.8)
Content type
Image
Digest
Size
73.9 MB
Last updated
about 5 years ago
docker pull mpdred/semantic-tagger