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

Fix semver not fully covered #1081

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Conversation

Lee-W
Copy link
Member

@Lee-W Lee-W commented Apr 24, 2024

Description

1.0.0-reallyweird is a valid semver but not yet covered by commitizen. Possible solution could be #950 (comment)

Closes: #950

Checklist

  • Add test cases to all the changes you introduce
  • Run ./scripts/format and ./scripts/test locally to ensure this change passes linter check and test
  • Test the changes on the local machine manually
  • Update the documentation for the changes

Expected behavior

Steps to Test This Pull Request

Additional context

@Lee-W
Copy link
Member Author

Lee-W commented Apr 24, 2024

Currently, only test cases are added. Will need to find some time to wrap it up. Feel free to take over if anyone's interested in it 🙂

@Lee-W
Copy link
Member Author

Lee-W commented Apr 25, 2024

I think this one would be a bit tricky 🤔 prerelease can be anything for semver. Thus, bump prerelease might not make sense to semver. e.g., what should be the next version of 1.1.0-test @woile @noirbizarre WDYT?

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

Successfully merging this pull request may close these issues.

Help wanted: commitizen 3.x not supoort generate CHANGELOG with tag format like v1.0.0-release
1 participant