-
Notifications
You must be signed in to change notification settings - Fork 3
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
Support non-SemVer and en dashes #22
Comments
Update: Sometimes, software uses keep-a-changelog, but do not follow SemVer. JabRef is one example. It would be nice if this tool was usable with JabRef, too. |
Hi @koppor, those seem like reasonable requests. I'm going to add a flag ( I've also updated it to allow more permissive version strings, instead of only SemVer. I took a look at the JabRef changelog, and saw that you guys have some very long changelog entries and went ahead and also added the ability to disable entry line wrapping and the ability to wrap at a custom character count ( I've got it in a PR (#23) for now, and will try and get a release out later today or tomorrow. |
One other thing I wanted to mention: The JabRef changelog has an "Older versions" section at the bottom of it, which is not really in line with Keep a Changelog and thus does not parse very well with This may still be acceptable for your use-cases, as I think you're just looking to diff things, but I'm not sure how to support that. |
@koppor I've released |
Released 0.9.1, should be all set now. |
When trying to parse https://github.com/JabRef/jabref/blob/v5.11/CHANGELOG.md,
version
is alwaysnull
. I think, it could be because of the used en dash. There is an issue, because the official format might permit en dash (see olivierlacan/keep-a-changelog#497; linked from nbbrd/heylogs#140 (comment)).If en dash support is "difficult" to implement, maybe this tool coud parse the github compare link to get the version out of that link?
(General background: I was recommended clparse at NiclasvanEyk/keepac#20 (comment))
The text was updated successfully, but these errors were encountered: