Skip to content

allow Symfony 4 components #22746

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

Closed
wants to merge 1 commit into from
Closed

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented May 18, 2017

Q A
Branch? 3.4
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets
License MIT
Doc PR

All requirements have been bumped to allow 4.0 versions of the Symfony
bridges, bundles, and components. The polyfill and Security Acl
component constraints have not been updated as they are released
independently. The same goes for the ClassLoader component which will
be removed in Symfony 4.

All requirements have been bumped to allow 4.0 versions of the Symfony
bridges, bundles, and components. The polyfill and Security Acl
component constraints have not been updated as they are released
independently. The same goes for the ClassLoader component which will
be removed in Symfony 4.
@xabbuh xabbuh force-pushed the allow-4.0-components branch from 461340b to dff6e47 Compare May 18, 2017 07:12
@xabbuh
Copy link
Member Author

xabbuh commented May 18, 2017

When this is merged up to the master branch we can think about whether we bump the requirements for 4.0 to always be ~3.4|~4.0 (we did something similar for Symfony 3.0 in #14296).

@xabbuh
Copy link
Member Author

xabbuh commented May 18, 2017

see #22742

@xabbuh xabbuh closed this May 18, 2017
@xabbuh xabbuh deleted the allow-4.0-components branch May 18, 2017 07:38
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