Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enhance GitHub dispatcher #5059

Open
junminahn opened this issue Feb 26, 2025 · 0 comments
Open

enhance GitHub dispatcher #5059

junminahn opened this issue Feb 26, 2025 · 0 comments

Comments

@junminahn
Copy link
Collaborator

junminahn commented Feb 26, 2025

We want to enhance the GitHub dispatcher logic to automatically determine the next tag version based on commit history if a tag is not provided by the GitHub UI:

  1. Major – If a commit includes a breaking change
  2. Minor – If a commit is of type feat
  3. Patch – For all other commit types

Additional info: (https://www.conventionalcommits.org/en/v1.0.0/#summary)
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant