5.0.6 tagged as a pre-release in GitHub?

[Montg0mery]

Is it correct that 5.0.6 is tagged as a non-stable pre-release, or is it actually a stable release that has just been tagged incorrectly on GitHub?

https://github.com/capstone-engine/capstone/releases/tag/5.0.6

Thanks.

[Rot127]

We usually wait three days before marking it latest. In case some people want to give feedback before.
But it lead to confusion before. We can consider changing our release procedure.

[Montg0mery]

We usually wait three days before marking it latest. In case some people want to give feedback before. But it lead to confusion before. We can consider changing our release procedure.

I think it's fine to wait 3 days. I guess part of my confusion is that it's marked as pre-release in GitHub but stable in PyPi: https://pypi.org/project/capstone/#history

[Rot127]

I think it's fine to wait 3 days. I guess part of my confusion is that it's marked as pre-release in GitHub but stable in PyPi: https://pypi.org/project/capstone/#history

I think pypip automatically tags full version numbers (without alpha, rc1 etc. postfix) as latest release. @kabeor checked this IIRC already. So one more reason to switch to a different release naming convention I guess.