suggestion: change the way rolling release work

[yuval-k]

currently kgateway has a rolling release that overrides the 2.1.0-main tag.
This is annoying for multiple reasons:

• creates notification spam
• messes up vscode pulling, as it needs to override git tags (tags are usually immutable)

Suggestions:

• not override the github tag, and not publish the release in github. instead, publish the instructions on how to use it in kgateway.dev

[nfuden]

Does this also mean that the package (ie images) wont be published?

For example if I want to have a reference to tip in a docker file one often would try to use @latest but right now would have to do @2.1.0-main .

Any thoughts on this? Or is that sufficiently niche?

I question as there was an issue / timing thing with building the envoy-wrapper image and one quick bandaid for unblocking control plane work was to just reference the image as published.

[timflannagan]

Yep, good question -- publishing "latest" artifacts on merges to main will still be supporting with this proposal. The only change here is we stop publishing GH release and the underlying git tag for the reasons that Yuval outlined above.

[timflannagan]

Update: #11290 has been merged to main. Latest artifacts are still published on pushes to main, but we're no longer maintaining a rolling release & underlying git tag.