CodeBleu commented on issue #109: URL: https://github.com/apache/cloudstack-terraform-provider/issues/109#issuecomment-2067741961
@rohityadavcloud Yes, this is the case: `I suppose the same thing has happened with Tofu, they need to delete old checksum/sha for their registry to re-registry the new tag+artifacts?` That is why I said: `The issue is not with new versions, the issue is when you update the release artifacts and SHAs in the repo, but do not change the version.` This appears to apply to both Terraform and Tofu registry. This is also why I mentioned this: `If there is some actual small changes with this provider that can benefit the community and do a minor patch version update to 0.5.1 then we all win!` So the question is, which one is quicker? 1. Your version bump with this -> `"...that needs to have a new RC put for vote and only then we can publish a new git tag."` 2. PR and merge with Tofu? If you choose 1, I think you or another maintainer of this repo should try creating a PR deleting [this](https://github.com/opentofu/registry/blob/7e4023585a04613a12dd150cec45e114788db02b/providers/c/cloudstack/cloudstack.json), and hopefully they can approve and merge it quickly. If not, then the Tofu users are going to have to wait until you all release another version :crying_cat_face: :wink: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
