Remove release_status property from all netkans #10413
Merged
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
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
#10283 removed
release_statusfrom all netkans that set it to anything other thanstableso they wouldn't be treated as prereleases and KSP-CKAN/CKAN#4260 could add support for prereleases.Turns out that setting it to
stablecauses problems as well, see #10397 for an example. The author of InfernalRoboticsNext reported that his mod had a prerelease indexed as a normal release in CKAN because of this.Now they're all purged, including frozen in case they're unfrozen in the future or used as templates by other authors.