Weird behavour/bug when latest tag ends with zero using --current and topo_order

[schancksb]

Hey there,
Honestly i don't know if this is a bug or I'm missing something, but when I bump the version of my python project, and the new version ends with zero (i.e.: v0.60.0) the following command git-cliff -o - --current --strip header produces the entire changelog including all tags interestingly this does not happen when the version tag ends with any other number (i.e. v0.60.2).

Initially I noticed this issue when a workflow in github actions to generate a release for the project would fail since the body is too long.
I don't know what might be causing this, if there is an error in my command/setup or if this is a bug.
I'd appreciate any insights.

Here is my config file (pyproject.toml):

[tool.git-cliff.git]
conventional_commits = true
filter_unconventional = true
split_commits = false
filter_commits = true
topo_order = true
sort_commits = "newest"
skip_tags = "^v0\\.([0-4]\\.[0-5]|[0-3]\\.[0-9])$"  # Skips v0.0.0 through v0.4.5

[tool.git-cliff.bump]
features_always_bump_minor = false
breaking_always_bump_major = false

NOTE: When I disable topo_order the output is what's expected, so I think it might have something to do with this issue.

[orhun]

Yup, this sounds like a similar issue described in #1080

First I was suspicious of the skip_tags regex but tested it with some values and it seems fine.