Skip to content

Jilu doesn't play nicely with incorrect formatted release tags #21

@MTRNord

Description

@MTRNord

Hi we switched to this and previously made tags that do not follow semver.

We have many that started with release- instead of v and have one starting with v (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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions