The version 0.5.0 doesn't have the prefix v. Is it an intentional change?

[suzuki-shunsuke]

https://github.com/astral-sh/ruff/releases/tag/0.5.0

I expected the version was v0.5.0, but actually it was 0.5.0.
I know 0.5.0 has some breaking changes, but this change isn't noted in the release note.
Is this an intentional change? Or just a miss?

[zanieb]

Yes this was an intentional change with our new release pipeline. Sorry it wasn't documented!

[suzuki-shunsuke]

Thank you for your quick answer! 👍

[charliermarsh]

Out of curiosity: where are you relying on it? I'm just trying to understand how / which consumers might be affected.

[suzuki-shunsuke]

I'm a creator of aqua, which is a CLI version manager.
aqua has an official registry and it supports ruff.
When a tool which the official registry supports releases a new version, a pull request is created to test if a new version can be installed correctly.
When ruff 0.5.0 was released, we found it's breaking changes because CI failed.

• chore: update astral-sh/ruff v0.4.10 to 0.5.0 aquaproj/aqua-registry#24368

We have already fixed the official registry to support ruff 0.5.0.

• fix(astral-sh/ruff): follow up changes of ruff 0.5.0 aquaproj/aqua-registry#24373

When I fixed the official registry, I found the version wasn't v0.5.0 but 0.5.0.

[Peiffap]

FYI, the pypi version badge in README.md still shows v0.5.0.

[charliermarsh]

I think that’s normal — that’s not based on the Git tag.