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
Please could you mark releases as "latest" (i.e. non pre-release) since this is messing with some automation in various repositories.
It's generally bad practice to use pre-release binaries in production, so therefore a lot of tooling is built to exclude these packages from automated updates and for selection during builds.
From reading older (closed) issues, there doesn't appear to be a real reason for these to be marked as pre-release, but please do let me know if there's a reason.
The text was updated successfully, but these errors were encountered:
Please could you mark releases as "latest" (i.e. non pre-release) since this is messing with some automation in various repositories.
It's generally bad practice to use pre-release binaries in production, so therefore a lot of tooling is built to exclude these packages from automated updates and for selection during builds.
I know next to nothing about goreleaser, however I can see
prerelease: true
being set.https://github.com/chainguard-dev/apko/blob/main/.goreleaser.yaml#L61
From reading older (closed) issues, there doesn't appear to be a real reason for these to be marked as pre-release, but please do let me know if there's a reason.
The text was updated successfully, but these errors were encountered: