Closed dekimsey closed 2 years ago
Hello, Thanks for pointing out that issue. This is rather unexpected, I'm sorry that it makes your installs fail :-/ I'll try to fix this somehow as soon as possible.
add tag 2.0.0, remove tag v2.0.0
Hello,
Sorry for the delay. I finally replaced the v2.0.0
tag with 2.0.0
and fixed the release.
Ansible Galaxy has been updated too.
I hope this won't break things for people using the v2.0.0
tag.
Thanks again for reporting this.
We've found our ansible-galaxy installs are failing recently and it appears to be related to frzk.chrony's change in tag format.
I have a requirements file like such:
Our builds are unable to execute now and I cannot figure out how to get Ansible to just use the given version. Please advise