Skip to content

WPCS 3.0: Composer updates#732

Closed
GaryJones wants to merge 7 commits intodevelopfrom
feature/composer-updates
Closed

WPCS 3.0: Composer updates#732
GaryJones wants to merge 7 commits intodevelopfrom
feature/composer-updates

Conversation

@GaryJones
Copy link
Contributor

We need VIPCS to be compatible with WPCS 3.0, so this is the first of a few PRs to address the known compatibility issues.

Composer: up the minimum PHPCS version to 3.7.1

PHPCS 3.7.1 adds support for PHP 8.1 features, including fixing a retokenization of reserved keywords bug in PHPCS 3.7.0. Amends a couple of GitHub workflows for this change too.

Composer: rename scripts

Brings them more in line with the Composer scripts in WPCS.

Composer: add script descriptions

Displayed for composer list.

Composer: use develop branch of WPCS

VIPCS must be compatible with WordPress Coding Standards 3.0.0, currently in development on its develop branch. WPCS now uses some extra dependencies, which are also in development, so we need to allow for a minimum-stability of dev. Run composer update -W to pull those extra dependencies in.

Composer: Normalize the order

Uses the composer-normalize plugin to keep a consistent order.

Note: GitHub Actions may report failures whilst this and the next few PRs go through, but I don't want to bundle all the changes into big PRs.

Add support for PHP 8.1 features, including fixing a retokenization of reserved keywords bug in PHPCS 3.7.0.
Brings them more into line with the Composer scripts in WPCS.
VIPCS needs to be compatible with WordPress Coding Standards 3.0.0, which is currently in development on its `develop` branch. WPCS now uses some extra dependencies, which are also in development, so we need to allow for a minimum-stability of dev. Run `composer update -W` to pull those extra dependencies in.
Uses the composer-normalize plugin to keep a consistent order.
@GaryJones GaryJones added this to the 3.x milestone Dec 20, 2022
@GaryJones GaryJones self-assigned this Dec 20, 2022
@GaryJones GaryJones requested a review from a team as a code owner December 20, 2022 02:10
Copy link
Collaborator

@jrfnl jrfnl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @GaryJones Thanks for setting this up. The PR is mixing a few changes with different decision points in one PR (Composer normalization and scripts changes vs changing versions of dependencies), but that's no biggie.

I've left a number of comments inline for your perusal.

Other than that, I'd like to suggest not changing the WPCS version to develop as that's a moving target.

I'm still hoping we reach the point where we can tag a 3.0.0-RC release before I leave for my break. Once that's tagged, the WPCS version for this repo could then be set to 3.0.0 (with minimum-stability set to RC), which makes it less of a moving target + makes it more descriptive what's going on.

@jrfnl
Copy link
Collaborator

jrfnl commented Dec 30, 2022

Note: if the change to WPCS develop would stay, the CI workflows should be updated for that change in the same commit.

GaryJones and others added 2 commits December 30, 2022 10:06
Co-authored-by: Juliette <663378+jrfnl@users.noreply.github.com>
Co-authored-by: Juliette <663378+jrfnl@users.noreply.github.com>
@GaryJones
Copy link
Contributor Author

The changes here are mostly now handled in

I've skipped the normalizing of the composer.json for now.

@GaryJones GaryJones closed this Jan 24, 2023
@GaryJones GaryJones deleted the feature/composer-updates branch June 20, 2023 19:53
@jrfnl jrfnl modified the milestones: 4.x, 3.x Aug 21, 2023
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