Set stability tolerance based on installing module #100
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.
Problem
In KSP-CKAN/NetKAN#10325, two modules with prereleases are being updated, but validation is failing because it is installing the prerelease of one module alongside the regular release of the other, which causes file overwrites:
In typical usage this would not happen because the overall prerelease setting would determine for both mods whether prereleases are available.
(A user who chooses to enable prereleases for just one of these two mods will have to learn to make better choices.)
Changes
Now when we install a mod, if it's a prerelease, then we enable all prereleases in the dummy instance. This will allow prereleases to be pulled in as dependencies when installing other prereleases.