Skip to content

[Conductor] Update friendsofphp/php-cs-fixer to v3.82.2#3

Merged
pscheit merged 1 commit intomainfrom
conductor-friendsofphp-php-cs-fixer-43521
Jul 10, 2025
Merged

[Conductor] Update friendsofphp/php-cs-fixer to v3.82.2#3
pscheit merged 1 commit intomainfrom
conductor-friendsofphp-php-cs-fixer-43521

Conversation

@private-packagist
Copy link
Copy Markdown
Contributor

This PR was automatically generated by Conductor.

The PR contains the changes generated by running the following command:

composer update friendsofphp/php-cs-fixer:v3.82.2 --with-all-dependencies --minimal-changes

Changelog

friendsofphp/php-cs-fixer (Source: GitHub Releases))

v3.82.2

What's Changed

  • fix: ClassAttributesSeparationFixer - handle method get aliased in trait import by @​kubawerlos in #8822
  • fix: VisibilityRequiredFixer - handle promoted property with visibility and reference, but without type by @​kubawerlos in #8823
  • fix: LowercaseStaticReferenceFixer - do not touch enum's cases by @​kubawerlos in #8824
  • fix: StatementIndentationFixer - multi constant statement containing array by @​gharlan in #8825

Full Changelog: v3.82.1...v3.82.2

v3.82.1

What's Changed

Full Changelog: v3.82.0...v3.82.1

v3.82.0

What's Changed

Full Changelog: v3.81.0...v3.82.0

v3.81.0

What's Changed

  • feat: VisibilityRequiredFixer - handle more than only the first promoted property by @​kubawerlos in #8801
  • fix: VisibilityRequiredFixer - handle promoted parameter passed by reference by @​kubawerlos in #8799
  • fix: BracesPositionFixer - do not throw error when variable is terminated by PHP close tag by @​paulbalandan in #8804
  • fix: PhpUnitInternalClassFixer - skip adding @​internal on instantiation of anonymous classes by @​paulbalandan in #8807
  • fix: PhpUnitDataProviderMethodOrderFixer - handle data provider defined by both annotation and attribute by @​kubawerlos in #8805
  • chore: add automatically to milestone "PHP 8.5 initial compatibility" if label is "topic/PHP8.5" by @​kubawerlos in #8806
  • chore: fail "Deployment checks" if any job from tests failed by @​kubawerlos in #8792
  • docs: update docs about --allow-unsupported-php-version by @​keradus in #8796

Full Changelog: v3.80.0...v3.81.0

v3.80.0

Long-awaiting official support for PHP 8.4 in PHP-CS-Fixer is finally here 🥳! We know, it's long overdue, but for a reason... Let us explain a bit, for transparency and clean atmosphere around the project.

First of all, we are fully aware that tool like Fixer should support new PHP releases from day 0, but in reality it's not that simple. The project has 3 (let's emphasise this: three) active maintainers, whose activity depends on many factors. Even though we take this responsibility very seriously, at the same time we need to prioritise our time and efforts. Sometimes it's just not meant to have focus on OSS, and there's nothing wrong about it. People often take OSS maintenance for granted, expecting that we (Fixer team) will provide solutions for their problems and needs, but we believe that the true nature of OSS is overlooked by many of them. It's not about you, it's not about maintainers - it's about the good of the project and its users. And most importantly: it's open for everyone to contribute. You want Fixer to support PHP 8.4? Great, then help with verifying if it works correctly on a 8.4-based sources, provide tests, fix bugs if any were found... That's how it should work in a healthy community. Fixer has many great contributors, but somehow support for new PHP releases is not the topic that engage them 😅. Yes, you could say "but if I work on Fixer in my free time, and I provide PR(s) related to new PHP version support, it still needs to be reviewed and merged, but since maintainers' activity is not reliable, it may end up forgotten and my time would have got wasted", and we really understand that concern. We can't guarantee either implementing stuff on our own, and reviewing contributed code, because we simply have our lifes, families, jobs, hobbies, and Fixer is "just" a side project that we like. We don't get paid for this, we do it because we want to bring value to the PHP community. But this can't be done at the expense of our private matters.

We will do our best to bring PHP 8.5 support faster, maybe even on day 0. But it also may be done half a year after its release. It depends - on us, on all of you. We encourage you to contribute to the project, let's grow Fixer together!

We thank all the people who participated in PHP 8.4 milestone no matter how - finding and reporting bugs, implementing features and fixes, providing feedback in the PRs or discussions. We all did it in the end, time to celebrate 🥳!

What's Changed

Full Changelog: v3.79.0...v3.80.0

v3.79.0

What's Changed

Full Changelog: v3.78.1...v3.79.0

v3.78.1

What's Changed

Full Changelog: v3.78.0...v3.78.1

v3.78.0

What's Changed

  • feat: VisibilityRequiredFixer - support promoted properties by @​kubawerlos in #8773
  • feat: BracesPositionFixer - support property hooks by @​kubawerlos in #8782
  • fix: StatementIndentationFixer - handle functions set and get (like property hooks, but not) by @​kubawerlos in #8576
  • fix: NativeFunctionInvocationFixer - fix global function set called in array key by @​kubawerlos in #8568
  • fix: StaticPrivateMethodFixer - handle nested calls by @​kubawerlos in #8768
  • fix: NoBreakCommentFixer - handle function having return type by @​kubawerlos in #8767
  • chore: VisibilityRequiredFixer - document behaviour for asymmetric visibility with only set-visibility by @​kubawerlos in #8783

Full Changelog: v3.77.0...v3.78.0

v3.77.0

What's Changed

  • chore: add automatically to milestone "PHP 8.4 initial compatibility" if label is "topic/PHP8.4" by @​kubawerlos in #8770
  • chore: fix adding automatically to milestone "PHP 8.4 initial compatibility" if label is "topic/PHP8.4" by @​kubawerlos in #8775
  • chore: fix adding automatically to milestone "PHP 8.4 initial compatibility" if label is "topic/PHP8.4" by @​kubawerlos in #8776
  • chore: move all indicators to analyzers by @​kubawerlos in #8772
  • chore: move PHP-compat integration tests by @​keradus in #8781
  • chore: partially apply NoExtraBlankLinesFixer:tokens.comma by @​keradus in #8762
  • chore: reconfigure phpdoc_order in local config by @​mvorisek in #8220
  • feat: CommentToPhpdocFixer and PhpdocToCommentFixer - support asymmetric visibility by @​kubawerlos in #8774
  • feat: NoEmptyStatementFixer - support abstract property hooks by @​kubawerlos in #8766
  • feat: NullableTypeDeclarationForDefaultNullValueFixer - support asymmetric visibility in the constructor by @​kubawerlos in #8604
  • feat: ProtectedToPrivateFixer - add support for promoted properties by @​kubawerlos in #8608
  • feat: PhpdocOrderFixer - extend support for phpstan and psalm annotations by @​keradus in #8777
  • feat: support anonymous classes extending TestCase in PHPUnit fixers by @​kubawerlos in #8707
  • fix: PhpUnitAttributesFixer - correctly remove annotations when configured ['keep_annotations' => false] by @​kubawerlos in #8577
  • fix: ProtectedToPrivateFixer - fix asymmetric visibility with only set visibility by @​kubawerlos in #8763

Full Changelog: v3.76.0...v3.77.0

Task options

If you close the PR, the task will be skipped and Conductor will schedule the next task. Clicking the "Skip" button in the UI has the same effect. Conductor won't attempt to update the dependency to this exact version again but it will schedule updates to newer versions.


Powered by Private Packagist

Conductor executed the following commands:
composer update friendsofphp/php-cs-fixer:v3.82.2 --with-all-dependencies --minimal-changes
@private-packagist
Copy link
Copy Markdown
Contributor Author

composer.lock

Dev Package changes

Package Operation From To About
friendsofphp/php-cs-fixer upgrade v3.76.0 v3.82.2 diff

Settings · Docs · Powered by Private Packagist

@pscheit pscheit merged commit 6a45ee1 into main Jul 10, 2025
1 check passed
@private-packagist private-packagist Bot deleted the conductor-friendsofphp-php-cs-fixer-43521 branch July 10, 2025 06:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant