Skip to content

Fix wrong requirements for ocramius/proxy-manager in root composer.json #31894

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

Merged
merged 1 commit into from
Jun 6, 2019

Conversation

henrikvolmer
Copy link

Q A
Branch? 4.2 for bug fixes
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #31891
License MIT

Fixed wrong requriement for ocramius/proxy-manager

@nicolas-grekas nicolas-grekas changed the title #31891 fix wrong requirements Fix wrong requirements for ocramius/proxy-manager in root composer.json Jun 6, 2019
@fabpot fabpot force-pushed the #31891-proxyManager branch from 32ced23 to ee98786 Compare June 6, 2019 12:58
@fabpot
Copy link
Member

fabpot commented Jun 6, 2019

Thank you @henrikvolmer.

@fabpot fabpot merged commit ee98786 into symfony:4.2 Jun 6, 2019
fabpot added a commit that referenced this pull request Jun 6, 2019
…composer.json (henrikvolmer)

This PR was squashed before being merged into the 4.2 branch (closes #31894).

Discussion
----------

Fix wrong requirements for ocramius/proxy-manager in root composer.json

| Q             | A
| ------------- | ---
| Branch?       |  4.2 for bug fixes
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #31891
| License       | MIT

Fixed wrong requriement for `ocramius/proxy-manager`

Commits
-------

ee98786 Fix wrong requirements for ocramius/proxy-manager in root composer.json
@fabpot fabpot mentioned this pull request Jun 6, 2019
@fabpot fabpot mentioned this pull request Jun 26, 2019
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.

5 participants