Skip to content

Conversation

@jrfnl
Copy link
Member

@jrfnl jrfnl commented Mar 18, 2020

Proposed Changes

Development for PHPCS 4.x has started in a new 4.0 branch.

This PR is two-fold:

  1. On the one hand, it adds testing against PHPCS 4.x to the Travis matrix as an early warning system in case any cross-version compatibility fixes would be needed for the plugin itself.
    The build against 4.x-dev has been added to allow_failures for now.
    Note: as PHPCompatibility currently doesn't allow for PHPCS 4.x (yet), I'm aliasing the install to 3.9.99 for testing purposes in the Travis build only.
  2. On the other hand, it allows installation in combination with PHPCS 4.x, which will in turn allow external standards which require this plugin, to start testing their standard against the PHPCS 4.x-dev branch.
    As it was now, external standards would get the plugin at version 0.4.4 as that's the last version with a PHPCS * constraint.

Related Issues

Development for PHPCS 4.x has started in a new `4.0` branch.

This PR is two-fold:

1. On the one hand, it adds testing against PHPCS 4.x to the Travis matrix as an early warning system in case any cross-version compatibility fixes would be needed for the plugin itself.
    The build against `4.x-dev` has been added to `allow_failures` for now.
    Note: as PHPCompatibility currently doesn't allow for PHPCS 4.x (yet), I'm aliasing the install to `3.9.99` for testing purposes in the Travis build only.
2. On the other hand, it allows installation in combination with PHPCS 4.x, which will in turn allow external standards which `require` this plugin, to start testing their standard against the PHPCS 4.x-dev branch.
    As it was now, external standards would get the plugin at version `0.4.4` as that's the last version with a PHPCS `*` constraint.
@Potherca Potherca merged commit 7c75210 into master Apr 6, 2020
@jrfnl jrfnl deleted the feature/allow-use-with-phpcs-4.x branch April 6, 2020 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants