Packages versions (>= 2.2.0) in release page are all only 2.2.

[4hiziri]

Packages versions (>= 2.2.0) in release page are all only 2.2.

If package version is 2.2.0, package name should be like validator-v2.2.0-linux-arm64.tar.gz.
Actually, previous version packages (< 2.2.0) are named like that (example, validator-v2.1.0-linux-arm64.tar.gz).
But packages after v2.2.0 have only version number 2.2 like validator-v2.2-linux-amd64.tar.gz (This is v2.2.1! you can't recognize package which has minor version, right?)

I want you to fix package name.
Because some package-manager can't recognize package version, like aqua.
But if you don't feel like solving this problem, please just close this issue.
Sorry for the hassle.

[kehoecj]

@4hiziri I can definitely fix this - thanks for bringing it to my attention! I recently changed the packaging workflow to include signed releases and this slipped in. @suzuki-shunsuke were you able to fix this for 2.2.1 and 2.2.2? Other package managers are including them so I'm hesitant to rename them. I can, however, upload correctly named binaries next to the existing ones. let me know if you'd like me to do this. I have a PR to fix it starting in >2.2.2.

[suzuki-shunsuke]

I've fixed our registry to support v2.2.0 or later.

https://github.com/aquaproj/aqua-registry/blob/85a1dd207fd2b2ed7a2f57aeb7b06724bec13baa/pkgs/Boeing/config-file-validator/registry.yaml#L57-L92

If you'll fix this issue at v2.2.3, I'll fix our registry again to support it.
You don't need to rename already released assets.

[4hiziri]

thanks, I love your tools!