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
Allow overriding git-semver-tags. #151
Comments
@samkelleher, thank you for explaining your use case. I was able to confirm that the
Personally I don't have time to work on this particular feature, but I have marked the issue as |
I've been working on this. Since non-semver suits my usecase, I'd preferable to use the package as is but pass in options. I've had success with this, however, the changlog outputted contains duplicate headers, due to the non-configurable line below. This line hardcodes semver detection and cannot be changed by passing in config options: This line uses semver by default, but can be replaced by options: So all thats needed is a config option for conventional-changelog-core and it'll all work as normal, providing you give it new regex to match tags on ( |
It's not possible to use the releaser tool unless you tag exactly with semver tags because it consumes the
git-semver-tags
package directly.This is the line:
https://github.com/conventional-changelog/releaser-tools/blob/master/packages/conventional-github-releaser/src/index.js#L50
For better or worse, I have a website project that doesn't use semver tags, but an incremental counter tag, so v1, v2, v3, v4, v18273 and so forth; and alas these are not picked up by the semver tags so I can't get nice changelogs released 😢
Even providing from/to GIT SHAs doesn't work because the git tags check is still performed regardless.
I suggest:
git-semver-tags
The text was updated successfully, but these errors were encountered: