Update to Drush 9 #136
Merged
Update to Drush 9 #136
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…task that is compatible with Drush 9.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The changes required to make
continuousphp/phing-drush-taskwork with Drush 9 were very small, but they are not merged to the original repo. So, I've released a fork from palantirnet/phing-drush-task on Packagist.Note that it is not possible to use Composer VCS repositories here, because those are only used if they're in a project's own root composer.json file... e.g. dependencies can't provide their own VCS sources.
Also, I think this will warrant a point release -- I'm also looking in to how this might affect existing projects and palantirnet/drupal-skeleton.