killianmuldoon
killianmuldoon
/close I think the fix in #8253 is a reasonable solution to this.
/reopen This has cropped up a few times since merging #8253. There's probably room for a more holistic fix, rather than just improving the error message.
>@killianmuldoon @sbueringer what is the idea here? if a release is not published we get the previous available? asking to see what y'all want That sounds like it would be...
In go modules versions are listed according to semantic versioning - it's the equivalent of: `go list -m -versions sigs.k8s.io/cluster-api`
> let's improve the error message to the users, informing them that this problem might happen if a release is being cut. I think one of the problems with this...
>Q: If we want to change it with v1.3 should we add it now to our migration doc as deprecation? (I'm not sure where we should put that info) Good...
The two API issues (I still have to create the second one) will work as enough documentation so we can add the deprecation notice whenever there's a new API version....
@Ab-hishek Sure - we'll probably activate a bunch of these changes just before the next release cycle. I'll ping here when we decide to unblock this.
/triage accepted