Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to PHPCSStandards/PHP_CodeSniffer & raise minimum supported version #805

Merged
merged 3 commits into from
Feb 10, 2024

Conversation

jrfnl
Copy link
Collaborator

@jrfnl jrfnl commented Dec 2, 2023

⚠️ This is a DRAFT PR on purpose as it references releases which have not yet been tagged. Once the PHPCS 3.8.0 tag is available (which contains the Composer replace directive) and the other dependencies have released, this can/should be merged and released ASAP. ⚠️


Switch to PHPCSStandards/PHP_CodeSniffer

The Squizlabs repo has been abandoned. The project continues in a fork in the PHPCSStandards organisation.

Ref:

Composer: raise the minimum supported PHPCS version to 3.8.0

... for improved PHP 8.2 support.

... to prevent end-users from running into trouble with the name change.

The files in the Composer vendor/bin will only be replaced when the replace... directive is found and that is only available in the 3.8.0 tag.
When the files in the Composer vendor/bin are not replaced, they will continue to point to the vendor/squizlabs/php_codesniffer directory which will no longer exist, leading to fatal "File not found" errors for end-users trying to run PHPCS/PHPCBF.

Includes updating references to the PHPCS version whenever relevant throughout the codebase.

Composer: update various version constraints

... after the tooling has also updated to the PHPCSStandards version of PHPCS.

Refs:

Changelog for the release of version 3.0.1


Closes #804

jrfnl added 2 commits December 7, 2023 04:22
The Squizlabs repo has been abandoned. The project continues in a fork in the PHPCSStandards organisation.

Ref:
* squizlabs/PHP_CodeSniffer 3932
@jrfnl jrfnl force-pushed the feature/switch-to-fork-of-phpcs branch from 62b9e9c to bf5c613 Compare December 7, 2023 03:27
@jrfnl
Copy link
Collaborator Author

jrfnl commented Dec 7, 2023

Update: The Composer package name will not change, so while this PR should still be merged at our convenience (after the 3.8.0 release, expected this Friday), we will not need to do a release to unblock end-users.

@jrfnl
Copy link
Collaborator Author

jrfnl commented Dec 8, 2023

PHPCS 3.8.0 has been released. (as well as PHPCSUtils 1.0.9 + PHPCSExtra 1.2.1)

Marking this PR as ready for review and retriggering the builds.

@jrfnl
Copy link
Collaborator Author

jrfnl commented Dec 8, 2023

Oh, and I will also remove the changelog commit from this PR as, now the Composer package name doesn't change, tagging a new release is not that urgent.

@jrfnl jrfnl force-pushed the feature/switch-to-fork-of-phpcs branch from bf5c613 to 873e28e Compare December 8, 2023 21:05
@jrfnl jrfnl marked this pull request as ready for review December 8, 2023 21:06
@jrfnl jrfnl requested a review from a team as a code owner December 8, 2023 21:06
@jrfnl
Copy link
Collaborator Author

jrfnl commented Jan 30, 2024

Just checking - any reason why this PR hasn't been merged yet ?

@GaryJones
Copy link
Contributor

Nope, no reason.

@jrfnl
Copy link
Collaborator Author

jrfnl commented Feb 10, 2024

Is it time to merge it maybe ? Asking again as there is another PR waiting on this one (which makes the test suite compatible with PHPUnit 8 + 9).

@GaryJones GaryJones merged commit 550ec3c into develop Feb 10, 2024
40 checks passed
@GaryJones GaryJones deleted the feature/switch-to-fork-of-phpcs branch February 10, 2024 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants