Release 4.2.3.6 (Lisias) for KSP >= 1.2.2

Lisias · Lisias · commit d127fc007bc1 · 2025-02-09T16:33:18.000-03:00
diff --git a/CHANGES.md b/CHANGES.md
@@ -2,6 +2,10 @@
 *Lasciate ogne speranza, voi ch'intrate*
 - - -
 
+* 2025-0209: 4.2.3.6 (Lisias) for KSP >= 1.2.2
+	+ More sensible warnings about the `:FOR[foo]:NEEDS[foo]` problem, avoiding flagging the occurrences where the problems are not triggered.
+	+ Reworks issues:
+		- [#31](https://github.com/KSP-ModularManagement/ModuleManager/issues/31) Warn when :FOR is used with :NEEDS using the same modName on the patch
 * 2025-0207: 4.2.3.5 (Lisias) for KSP >= 1.2.2
 	+ Fixes a pretty nasty Log Spam I let pass trough
 	+ Log a warning when `:FOR` and `:NEEDS` on the same patch uses the same identifier, as this will not work exactly as one would expect.
diff --git a/CHANGE_LOG.md b/CHANGE_LOG.md
@@ -2,6 +2,10 @@
 *Lasciate ogne speranza, voi ch'intrate*
 - - -
 
+* 2025-0209: 4.2.3.6 (Lisias) for KSP >= 1.2.2
+	+ More sensible warnings about the `:FOR[foo]:NEEDS[foo]` problem, avoiding flagging the occurrences where the problems are not triggered.
+	+ Reworks issues:
+		- [#31](https://github.com/KSP-ModularManagement/ModuleManager/issues/31) Warn when :FOR is used with :NEEDS using the same modName on the patch
 * 2025-0207: 4.2.3.5 (Lisias) for KSP >= 1.2.2
 	+ Fixes a pretty nasty Log Spam I let pass trough
 	+ Log a warning when `:FOR` and `:NEEDS` on the same patch uses the same identifier, as this will not work exactly as one would expect.
diff --git a/ModuleManager.122.version b/ModuleManager.122.version
@@ -8,7 +8,7 @@
 		"MAJOR":4,
 		"MINOR":2,
 		"PATCH":3,
-		"BUILD":5
+		"BUILD":6
 		},
 	"KSP_VERSION":{
 		"MAJOR":1,
diff --git a/ModuleManager.version b/ModuleManager.version
@@ -8,7 +8,7 @@
 		"MAJOR":4,
 		"MINOR":2,
 		"PATCH":3,
-		"BUILD":5
+		"BUILD":6
 		},
 	"KSP_VERSION_MIN":{
 		"MAJOR":1,
