Update WPCS to dev-develop branch at a specific commit

[mukeshpanchal27]

Closes #136

How to test the Change

1. Take the pull from the branch.
2. Set phpVersion: 8.1 in your .wp-env.json file and restart environment.
3. Update composer. Use composer update command.
4. Go to Admin Panel > Tools > Plugin Check > Check plugin

Checklist:

• I agree to follow this project's Code of Conduct.

[mukeshpanchal27]

PHPCS shows - The package "wp-coding-standards/wpcs" is pointing to a commit-ref, this is bad practice and can cause unforeseen issues. error because we use unstable version.

[swissspidy]

The warning is coming from composer validate --strict specifically, not PHPCS. It's usually just a warning, but --strict makes it error.

The only way to resolve this is by not using --strict for the time being.

Aside, a note from the Composer docs about using explicit commit references:

This feature has severe technical limitations, as the composer.json metadata will still be read from the branch name you specify before the hash. You should therefore only use this as a temporary solution during development to remediate transient issues, until you can switch to tagged releases. The Composer team does not actively support this feature and will not accept bug reports related to it.

It's definitely a temporary solution in this case, so IMHO it should be fine to temporarily remove --strict as well.

[spacedmonkey]

@mukeshpanchal27 The composer install is now failing in CI.

[mukeshpanchal27]

@swissspidy, the CI still shows that warning and throws the error.

[swissspidy]

The warning is expected to be there still. The step still fails now because of the additional The lock file is not up to date with the latest changes in composer.json error. That is new.

[mukeshpanchal27]

Thanks, @spacedmonkey, for helping me correct the composer version issue.