From ff252949c89e18a63e0a33262dfb99861844e01a Mon Sep 17 00:00:00 2001 From: Imani Manyara Date: Sun, 6 Sep 2026 08:44:46 -0400 Subject: [PATCH] Floor laravel/pint at the version whose output is committed The prefer-lowest leg installs the declared floor, and Pint's floor was old enough to format differently from the version that produced the committed code. Measured on laranail/db-tools: `laravel/pint: ^1.18` resolves 1.18.0 under --prefer-lowest, and `laranail-pint --test` FAILS against it while passing on 1.30.x. laranail/chrono hit exactly this and went red on prefer-lowest while prefer-stable was green. So the floor moves to ^1.30 - the line whose output is what is actually in the repository. Verified rather than assumed: with this constraint --prefer-lowest installs 1.30.0, and laranail-pint passes against it on both db-tools (159 reformatted files) and console (210). Pint is require-dev, so this is invisible to consumers: it constrains nothing they install. It only stops the lowest leg testing a formatter that disagrees with the code it is checking. Deliberately NOT applied to rector: at its ^2.5.8 floor Rector resolves 2.5.8 and PASSES, because it reports what it *would* change and an older release carries fewer rules. Flooring it would be churn with no failure behind it. --- composer.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/composer.json b/composer.json index 628d66d..82ef3a9 100644 --- a/composer.json +++ b/composer.json @@ -89,7 +89,7 @@ "laranail/validation-js": "^0.1", "larastan/larastan": "^3.9.3", "laravel/pao": "^1.1", - "laravel/pint": "^1.29", + "laravel/pint": "^1.30", "livewire/livewire": "^3.0||^4.0", "mrpunyapal/rector-pest": "^0.2.7", "nunomaduro/collision": "^8.0",