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

Allow testing against doctrine/common 2.6 #888

Merged
merged 1 commit into from
Aug 21, 2015
Merged

Allow testing against doctrine/common 2.6 #888

merged 1 commit into from
Aug 21, 2015

Conversation

nicolas-grekas
Copy link
Member

By forbidding 2.6-dev, dbal 2.5 is untestable, because when composer tries to resolve deps to their highest, it has two choices:

  • doctrine/common@dev-master + dbal@2.4
  • or doctrine/common@2.5 + dbal@dev-master

and it chooses the first option.

@doctrinebot
Copy link

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DBAL-1273

We use Jira to track the state of pull requests and the versions they got
included in.

deeky666 added a commit that referenced this pull request Aug 21, 2015
Allow testing with doctrine/common 2.6
@deeky666 deeky666 merged commit 3ad19b4 into doctrine:master Aug 21, 2015
@deeky666
Copy link
Member

@nicolas-grekas thanks!

@deeky666
Copy link
Member

@nicolas-grekas I suppose this needs to be backported to 2.5???

@nicolas-grekas
Copy link
Member Author

Not sure it's required but why not yes

@Ocramius Ocramius changed the title Allow testing with doctrine/common 2.6 Allow testing against doctrine/common 2.6 Jul 22, 2017
@Ocramius Ocramius added this to the 2.6 milestone Jul 22, 2017
@Ocramius Ocramius assigned Ocramius and deeky666 and unassigned Ocramius Jul 22, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants