#48: feature - remove prerelease flag & set the GitHub release to latest on post release #55
Conversation
This file contains hidden or 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
…to latest on post release
Contributor
Author
|
Fixes #48 |
jamesfredley
approved these changes
Oct 6, 2025
Contributor
|
@jdaugherty I'm probably misunderstanding this change, but why would we remove the "Pre-release" status from a GitHub release and always set it to latest (do we want releases for earlier version branches to be set as "latest"? |
Contributor
|
@matrei During the 72 hour vote window the GitHub release exists and is marked as Pre-release until after the vote finishes and it it fully published to maven central and sdkman. |
Contributor
|
@jamesfredley Aha, it was my understanding that a pre-release is a Milestone or RC. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
No description provided.