-
Notifications
You must be signed in to change notification settings - Fork 6
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
Jilu doesn't play nicely with incorrect formatted release tags #21
Comments
The default template did generate this: Wrong
Expected is this: Expected
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi we switched to this and previously made tags that do not follow semver.
We have many that started with
release-
instead ofv
and have one starting withv
(v0.1.0).While it correctly ignores the release- ones (thats totally fine) it now causes a weird bug. We now had made a v0.23.0 tag and have the super old v0.1.0 Tag. But instead of putting the v0.23.0 changes under that part in the changelog it actually seems to put the changes under the 0.1.0 release.
I am not sure if thats because we had many invalid tags or the problem is elsewhere. But it also lists only changes from the last incorrect tag until 0.23.0. And not from 0.1.0 to 0.23.0. So it seems to correctly filter them but puts the into the wrong version.
The text was updated successfully, but these errors were encountered: