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

Update Composer dependencies to latest #376

Closed
wants to merge 2 commits into from

Conversation

danielbachhuber
Copy link
Contributor

Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 0 installs, 15 updates, 2 removals
  - Removing symfony/debug (v3.4.12)
  - Removing psr/log (1.0.2)
  - Updating symfony/polyfill-ctype (v1.8.0 => v1.9.0): Loading from cache
  - Updating symfony/yaml (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/polyfill-mbstring (v1.8.0 => v1.9.0): Loading from cache
  - Updating symfony/translation (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/event-dispatcher (v3.4.12 => v3.4.15):  Checking out b2e1f19280
  - Updating symfony/dependency-injection (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/console (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/filesystem (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/config (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/class-loader (v3.4.12 => v3.4.15): Loading from cache
  - Updating behat/behat (v3.4.3 => v3.5.0): Loading from cache
  - Updating symfony/dom-crawler (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/css-selector (v3.4.12 => v3.4.15): Loading from cache
  - Updating symfony/browser-kit (v3.4.12 => v4.1.4): Loading from cache
  - Updating fabpot/goutte (v3.2.2 => v3.2.3): Loading from cache
Writing lock file
Generating autoload files

```
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 0 installs, 15 updates, 2 removals
  - Removing symfony/debug (v3.4.12)
  - Removing psr/log (1.0.2)
  - Updating symfony/polyfill-ctype (v1.8.0 => v1.9.0): Loading from cache
  - Updating symfony/yaml (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/polyfill-mbstring (v1.8.0 => v1.9.0): Loading from cache
  - Updating symfony/translation (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/event-dispatcher (v3.4.12 => v3.4.15):  Checking out b2e1f19280
  - Updating symfony/dependency-injection (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/console (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/filesystem (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/config (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/class-loader (v3.4.12 => v3.4.15): Loading from cache
  - Updating behat/behat (v3.4.3 => v3.5.0): Loading from cache
  - Updating symfony/dom-crawler (v3.4.12 => v4.1.4): Loading from cache
  - Updating symfony/css-selector (v3.4.12 => v3.4.15): Loading from cache
  - Updating symfony/browser-kit (v3.4.12 => v4.1.4): Loading from cache
  - Updating fabpot/goutte (v3.2.2 => v3.2.3): Loading from cache
Writing lock file
Generating autoload files
```
@danielbachhuber danielbachhuber added this to the 1.5.1 milestone Sep 5, 2018
@danielbachhuber
Copy link
Contributor Author

@ataylorme Are you fine updating the tested versions to PHP 7.1?

@ataylorme
Copy link
Contributor

@danielbachhuber I am okay with this as the default PHP version for WordPress sites on Pantheon is 7.2.

That being said if the Symfony dependencies require PHP 7.1 and we are dropping older PHP support then we should make a new release for 2.x and document PHP 7.1 as a requirement for the 2.x version

@danielbachhuber
Copy link
Contributor Author

That being said if the Symfony dependencies require PHP 7.1 and we are dropping older PHP support then we should make a new release for 2.x and document PHP 7.1 as a requirement for the 2.x version

Works for me. Do you want to take care of this and release?

@ataylorme
Copy link
Contributor

I can take care of cutting the release but I don't have bandwidth until Friday or next week at the earliest. Anything else you want to get into a release?

I would also like to get a +1 from @joshkoenig on dropping support for PHP < 7.1 and doing a major release.

@ataylorme ataylorme requested a review from joshkoenig September 5, 2018 16:03
@ataylorme
Copy link
Contributor

Anything else you want to get into a release?

Some candidates could be #353, #359, #347, #206 and #205

@danielbachhuber
Copy link
Contributor Author

I can take care of cutting the release but I don't have bandwidth until Friday or next week at the earliest. Anything else you want to get into a release?

Ok, let's do early next week then. I've assigned myself to #353, #347, #206 and will flag you for review when they're ready.

@ataylorme
Copy link
Contributor

Sounds good. I changed the 1.5.1 milestone to 2.0.0 and added those issues to it.

@danielbachhuber danielbachhuber removed this from the 2.0.0 milestone Sep 7, 2018
@danielbachhuber
Copy link
Contributor Author

Closing in favor of #379 which includes the Solarium update.

@danielbachhuber danielbachhuber deleted the composer-updates-1-5-1 branch September 7, 2018 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants