build(deps): update friendsofphp/php-cs-fixer requirement from ^3.76 to ^3.80 in /tools

[dependabot]

Updates the requirements on friendsofphp/php-cs-fixer to permit the latest version.

Release notes

Sourced from friendsofphp/php-cs-fixer's releases.

v3.80.0 Alexander

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

• feat: PHP 8.4 compatibility support by @​Wirone, @​kubawerlos, @​keradus and others in PHP-CS-Fixer/PHP-CS-Fixer#8300

Full Changelog: PHP-CS-Fixer/PHP-CS-Fixer@v3.79.0...v3.80.0

Changelog

Sourced from friendsofphp/php-cs-fixer's changelog.

Changelog for v3.80.0

• feat: PHP 8.4 compatibility support (#8300)

Changelog for v3.79.0

• chore: VisibilityRequiredFixerTest - run tests in correct PHP version (#8790)
• feat: BracesPositionFixer - do not touch one-line properties with hooks (#8785)
• feat: PhpUnitDataProvider(.+)Fixer - support attributes (#8197)

Changelog for v3.78.1

• fix: VisibilityRequiredFixer - do not add public incorrectly (#8787)

Changelog for v3.78.0

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

Changelog for v3.77.0

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

Changelog for v3.76.0

... (truncated)

Commits

• e49ed46 prepared the 3.80.0 release
• e9d1fe9 feat: PHP 8.4 compatibility support (#8300)
• 2434369 bumped version
• 366cf05 prepared the 3.79.0 release
• 51491b6 feat: PhpUnitDataProvider(.+)Fixer - support attributes (#8197)
• 5776c1d chore: VisibilityRequiredFixerTest - run tests in correct PHP version (#8790)
• 143160b feat: BracesPositionFixer - do not touch one-line properties with hooks (#8...
• 983f7f0 bumped version
• 112604b prepared the 3.78.1 release
• cdd2ea0 fix: VisibilityRequiredFixer - do not add public incorrectly (#8787)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.00%. Comparing base (522fbf9) to head (7a14093).
Report is 1 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@ ## main #134 +/- ## ========================================= Coverage 96.00% 96.00% Complexity 490 490 ========================================= Files 36 36 Lines 1528 1528 ========================================= Hits 1467 1467 Misses 61 61 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.