Coerce StarshipExpansionProject versioning into consistency #10319
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
|
Hey I didn’t see this before you merged it but this fix is the wrong way round. The leading . causes issues with the KSPBuildTools versioning input so its being dropped from all further releases in the future. |
|
Yes, I assumed that. |
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.
This mod's last three versions are:
https://github.com/Kari1407/Starship-Expansion-Project/releases
v.2.1.0v.2.2.0v3.0.0-b1(a pre-release)It currently has an out-of-order inflation error because the dot after the v is dropped in the pre-release.
Now we put the dot back.
We also have to set the
abstractbecause it isn't set on the GitHub repo.