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

PHP_CodeSniffer moved - we need to update our dependencies #168

Closed
GuySartorelli opened this issue Dec 3, 2023 · 2 comments
Closed

PHP_CodeSniffer moved - we need to update our dependencies #168

GuySartorelli opened this issue Dec 3, 2023 · 2 comments

Comments

@GuySartorelli
Copy link
Member

GuySartorelli commented Dec 3, 2023

See squizlabs/PHP_CodeSniffer#3932

tl;dr: We need to update our dependencies from squizlabs/php_codesniffer to phpcsstandards/php_codesniffer

There is one note in that issue that's relevant beyond just change the dependency:

Note: I would recommend waiting to make the switch until the 3.8.0 release has been tagged. Watch releases on the new repo to automatically get notified of this. The changelog will contain the relevant information for making the switch.

Notes

  • The original maintainer of codesniffer has not commented on that issue at the time of creating this issue. There is a chance it's some elaborate phishing ploy or similar, though that seems unlikely.
@jrfnl
Copy link

jrfnl commented Dec 7, 2023

Thank you for your support and your enthousiasm embracing the take-over of the PHP_CodeSniffer package.

In contrast to earlier information, arrangements are now being made to allow the package to continue under its original name on Packagist. The commit (in the new repo) to rename the package has been reverted.

Sorry for the confusion and thank you for understanding. I hope you'll enjoy the 3.8.0 release, which I expect to release this Friday.

P.S.: and no, this is not a phishing attempt, the repo change for PHP_CodeSniffer is real (and the original maintainer has confirmed this in the ticket now as well)

@GuySartorelli
Copy link
Member Author

Awesome, thank you for that information. I'll close this issue as there's no longer any action for us to take.

@GuySartorelli GuySartorelli closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants