Alpha or pre releases?

[illume]

Is your feature request related to a problem? Please describe.

We'd like to make alpha or pre-releases (or some other tag), and have those releases marked as alpha releases. But also have stable releases at the same time. Eg. I'd releases version 1.0.0 but do an alpha release for 1.1.0. This is for the artifact type Headlamp plugins (but I guess this is applicable for other types).

Is this already possible somehow? Any advice on how to achieve this would be much appreciated.

Describe the solution you'd like

Some way that people could tag their releases as alpha releases, but also release their artifacts.

Describe alternatives you've considered

People can encode this information in their version numbers, so I thought that could be a way to implement this... if there's not another way people are using. Then we could consider versions like 1.1.0-alpha.1 an alpha release, and show the user by default the most recent non-alpha release... for example: 1.0.0.

Container images (and npm packages) can have an alpha or latest tag.

[tegioz]

Hi @illume 👋

You can tag Headlamp plugins packages versions as prerelease using the prerelease field in the metadata file:

hub/docs/metadata/artifacthub-pkg.yml

Line 24 in 10997a4

prerelease: Whether this package version is a pre-release (optional, boolean)

[illume]

Thanks

[illume]

The prerelease config will be good for pre-releases.

Is there a concept of tags? The common use is for “alpha”, “nightly” or “latest” used in container images and also with other ones like npm packages and github releases. Where as some other systems use the version number.

[illume]

Ah, I found this discussion from last year where someone asked about channels in helm.

#4016

So unless something has changed in the last year, that answers my question: There’s no channels/tag concept… but it can be done by having separate repos.

[tegioz]

Yes, that's right. The only artifact kind with support for channels at the moment are OLM operators.