From 0badf6227834a29108f39ee16bf4b32d99b9e880 Mon Sep 17 00:00:00 2001 From: Rod Vince Date: Mon, 10 Aug 2026 22:45:06 -0600 Subject: [PATCH] fix: require milpa/command ^0.7, the only range this package can run in MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PluginOperations imports Milpa\Command\Effect\Subject and uses it fifteen times. That class does not exist before command v0.7.0, while composer.json declared ^0.6 as acceptable. Verified by execution rather than by reading the constraint: with command v0.6.0 resolved, composer installs happily and calling operations() dies on Class "Milpa\Command\Effect\Subject" not found. The declaration was false, not merely stale. The constraint narrows rather than widens, which is the point — it turns a silent runtime death into a composer-time conflict. Suite green at 391 tests. This is the same defect devtools v0.14.0 shipped with, fixed in v0.14.1. Refs greenhouse decisions/0025. --- composer.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/composer.json b/composer.json index 1003e76..85c31b6 100644 --- a/composer.json +++ b/composer.json @@ -21,7 +21,7 @@ "require": { "php": ">=8.3", "milpa/core": "^0.6.2 || ^0.7", - "milpa/command": "^0.6 || ^0.7", + "milpa/command": "^0.7", "milpa/events": "^0.2", "milpa/resolver": "^0.5.2 || ^0.6", "psr/log": "^3",