You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: alpha/beta releases are vended as latest/stable in Linux package repos, at least
Context: Sometimes we need to publish an alpha/beta release in GitHub. That's cool, but the way we're building the Linux packages causes the alpha/beta to sort with a higher version in APT/DNF, so they're preferred over the stable release of the same major.minor.micro version, e.g., v1.2.6-beta2 is considered "latest" by APT even when v1.2.6 is released, but stable should always be higher.
Possible solutions:
filter out alpha/beta versions when promoting releases downstream from GitHub, such as Linux packages and Docker images.
change the way the downstream release artifacts are built and promoted so they're always sorted lower than a stable release of the same m.m.m
I'm leaning toward simply NOT promoting alpha/beta downstream.
The text was updated successfully, but these errors were encountered:
Problem: alpha/beta releases are vended as latest/stable in Linux package repos, at least
Context: Sometimes we need to publish an alpha/beta release in GitHub. That's cool, but the way we're building the Linux packages causes the alpha/beta to sort with a higher version in APT/DNF, so they're preferred over the stable release of the same major.minor.micro version, e.g.,
v1.2.6-beta2
is considered "latest" by APT even whenv1.2.6
is released, but stable should always be higher.Possible solutions:
I'm leaning toward simply NOT promoting alpha/beta downstream.
The text was updated successfully, but these errors were encountered: