search

spinkube / spin-plugin-kube

A Spin plugin for interacting with Kubernetes.
Other
27 stars 7 forks source link

Remove `canary` releases #48

Closed endocrimes closed 7 months ago

endocrimes commented 8 months ago

We don't do mutable tags in SpinKube projects where avoidable due to their frequent issues and overhead when trying to understand the bits you are installing.

Is there a reason to have canary releases rather than artifacts on commits that can be fetched by those who want to use them?

If not please can we drop those before we cut our first releases?

bacongobbler commented 8 months ago

IIRC github artifacts only live for a certain number of days before they're purged from the system. Is there a way to change that?

I personally don't see an issue about shipping a canary release of the plugin. Users want the ability to test the absolute latest version. Pointing to a mutable tag vs pointing to a "rolling immutable tag" doesn't really make a difference to the end user: the user just wants the ability to test the latest changes.

My only requirement is that we want some way to allow users to install the latest version of the plugin. Currently we ask the user to run the following:

$ spin plugins install --url https://github.com/spinkube/spin-plugin-k8s/releases/download/canary/k8s.json

We'd need to update the README to use a "mutable" URL that will allow the user to download the latest version of the plugin. That way we won't need to update the README every time we ship a new commit.

bacongobbler commented 7 months ago

Coming back to this conversation. I think it'd be okay to ask developers to compile from source if they want the latest version for now. We can remove the canary release for the time being, then revisit whether we want to introduce some form of a canary release when requested by the community.

WDYT?

bacongobbler commented 7 months ago

canary tag and release has been dropped.