Skip to content

change commit messages and versioning to the semantic way #45

@genofire

Description

@genofire

i prefer the use of semantic-release.
Thats create automaticaly releases semantic-version based an conventional commits.

So every commit message must have the conventional commit standard:

  • fix(component): for bugfix
  • feat(component): for features
  • chore(docs): for docs
  • an ! in the prefix. e.g. (component)!: for breaking change (which create a new major version)

i switch that already for yanic ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions