Set x_netkan_allow_out_of_order for backporting mods #7528
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
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.
Motivation
In KSP-CKAN/CKAN#2824 and KSP-CKAN/NetKAN-Infra#102, we are automating version "epoch" management so that mod versions will be interpreted in chronological order.
This is undesirable for a few mods, specifically those that sometimes intentionally release a lower version of a mod after a later version, for example to backport fixes to earlier game versions.
Changes
Now the following mods have
x_netkan_allow_out_of_orderset to true because they have a history of intentional/valid out of order releases:Backports/KopernicusKSPInterstellarExtendedThis will ensure that these mods will not be auto-epoched.
Note that this property is not in the spec yet, but it will be after KSP-CKAN/CKAN#2824 is merged. It is important to set it before then, though, to prevent backports from accidentally being auto-epoched after merge.