fix(ci): mark GitHub releases as latest from prerelease #1277
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Do I need to setup a PGP key in order to commit to this repository? |
p5
changed the title
|
a new release got cut and marked as latest; and there is no need to default to marking things as latest, as we can always edit a release after all the artifacts are built. |
|
and we keep forgetting to mark releases as released. |
xnox
approved these changes
Sep 30, 2024
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1276
Closes #639
By using pre-releases, new updates are not discoverable by users and tooling. GitHub does not promote these as much, and tools like Renovate and Dependabot will exclude all pre-release packages by default.
This PR changes the Goreleaser configuration to no longer create pre-release packages, and instead create proper releases which will be available at the https://github.com/chainguard-dev/apko/releases/latest URL.
While I do not know anything about goreleaser, there is a
prerelease: trueline which does look to be the cause for this.This appears to have been set when GoReleaser was first introduced to this repository over two years ago, and I assume may have been something that has been overlooked.