Update compatibility for KSP 1.12.5#860
Closed
Sean-Kenneth-Doherty wants to merge 1 commit into
Closed
Conversation
Sean-Kenneth-Doherty
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
1.9.131.12.5Why
CKAN and AVC currently see the latest release as compatible through KSP 1.12.1. I rebuilt the plugin against a local KSP 1.12.5 install and updated the version metadata so maintainers have a small compatibility-update branch to review.
Related: #849
Validation
Built locally on Linux with Mono/xbuild against KSP
1.12.5.3190managed assemblies:Additional checks:
python -m json.tool GameData/RemoteTech/RemoteTech.versionmonodis --customattr GameData/RemoteTech/Plugins/RemoteTech.dllshowsAssemblyFileVersion("1.9.13")RemoteTech.dllis included underGameData/RemoteTech/Plugins/I did not run an in-game smoke test; opening as draft so maintainers can decide whether runtime QA or a different release version should be used.