It would be handy to have a way to ignore prereleases when not using an explicit --tag. That is, with GitLab, the current behavior is to install the latest release, even if that release number as a semver prerelease label, i.e. something like 0.1.0-dev.3. But this is typically not what a user would want: they'll generally want the latest "full" release.
On GitHub, releases can be explicitly marked as "prereleases", and the latest release is never a prerelease. So I suspect ubi already has the right default behavior for GitHub.
However, sometimes the user will want to use the latest prerelease. This is possible using --tag if the user knows which prerelease they want, but it would be handy to be able to let the tool find the latest prerelease (...which, as mentioned above, is already the default behavior for GitLab). So it would be nice to have a flag, something like --permit-prerelease, to explicitly opt-in to using GitHub prereleases and GitLab releases with prerelease-labels in the tags.
It would be handy to have a way to ignore prereleases when not using an explicit
--tag. That is, with GitLab, the current behavior is to install the latest release, even if that release number as a semver prerelease label, i.e. something like0.1.0-dev.3. But this is typically not what a user would want: they'll generally want the latest "full" release.On GitHub, releases can be explicitly marked as "prereleases", and the
latestrelease is never a prerelease. So I suspectubialready has the right default behavior for GitHub.However, sometimes the user will want to use the latest prerelease. This is possible using
--tagif the user knows which prerelease they want, but it would be handy to be able to let the tool find the latest prerelease (...which, as mentioned above, is already the default behavior for GitLab). So it would be nice to have a flag, something like--permit-prerelease, to explicitly opt-in to using GitHub prereleases and GitLab releases with prerelease-labels in the tags.