Update PHP-CS-Fixer to v3.88.2.#405
Merged
taylorotwell merged 1 commit intolaravel:mainfrom Oct 8, 2025
Merged
Conversation
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
2 participants
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.
A minor version bump to v3.88.2 with the addition of a name change to a rule in resources/presets/laravel.php.
The visibility_required rule was deprecated in favor of the modifier_keywords rule in PHP-CS-Fixer v3.88. From what I can see it's just a change to the rule name with the configuration and function of the fixer remaining the same.
There is a proxy in PHP-CS-Fixer that maintains compatibility with rule sets using the visibility_required name so pint users that use it in a custom configuration should be fine. Even so, I have altered the laravel ruleset since it is deprecated.
For reference, the PR to PHP-CS-Fixer that introduced the change: PHP-CS-Fixer/PHP-CS-Fixer#8995.