Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Security] [Ldap] [Easy-Pick] Limit ldap component version for branch 3.0 #17588

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
Feb 1, 2016
Merged

[Security] [Ldap] [Easy-Pick] Limit ldap component version for branch 3.0 #17588

merged 1 commit into from
Feb 1, 2016

Conversation

csarrazi
Copy link
Contributor

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

As the Ldap component will introduce BC changes for version 3.1 of Symfony, this PR limits the version to use in composer dependencies. This way, we can ensure that running composer update won't try to install the 3.1 Ldap component with version 2.8 or 3.0 of the Security component, Security Core component and SecurityBundle.

The required version will be changed in PR #17577, so version 3.1 of Symfony actually uses only version 3.1 onwards of the Ldap component.

@csarrazi csarrazi changed the title [Security] Limit ldap component version for branch 3.0 [Security] [Easy-Pick] Limit ldap component version for branch 3.0 Jan 28, 2016
@csarrazi csarrazi changed the title [Security] [Easy-Pick] Limit ldap component version for branch 3.0 [Security] [Ldap] [Easy-Pick] Limit ldap component version for branch 3.0 Jan 28, 2016
@csarrazi
Copy link
Contributor Author

csarrazi commented Feb 1, 2016

Fixed a typo.

Let's wait for the tests to run, but it should be good to go, @nicolas-grekas.

@nicolas-grekas
Copy link
Member

👍

@csarrazi
Copy link
Contributor Author

csarrazi commented Feb 1, 2016

Tests are broken, for another reason.

@csarrazi
Copy link
Contributor Author

csarrazi commented Feb 1, 2016

By the way, this currently blocks #17560 and #17577.

It will also make it possible to merge both PRs in a single PR.

@fabpot
Copy link
Member

fabpot commented Feb 1, 2016

Thank you @csarrazi.

@fabpot fabpot merged commit 1391311 into symfony:3.0 Feb 1, 2016
fabpot added a commit that referenced this pull request Feb 1, 2016
…on for branch 3.0 (csarrazi)

This PR was merged into the 3.0 branch.

Discussion
----------

[Security] [Ldap] [Easy-Pick] Limit ldap component version for branch 3.0

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

As the Ldap component will introduce BC changes for version 3.1 of Symfony, this PR limits the version to use in composer dependencies. This way, we can ensure that running composer update won't try to install the 3.1 Ldap component with version 2.8 or 3.0 of the Security component, Security Core component and SecurityBundle.

The required version will be changed in PR #17577, so version 3.1 of Symfony actually uses only version `3.1` onwards of the Ldap component.

Commits
-------

1391311 Limit Ldap component version for the 3.0 branch
@csarrazi csarrazi deleted the feat-limit-ldap-version branch February 1, 2016 19:56
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