8000 [BrowserKit] Bump the dom-crawler minimum version requirement by jakzal · Pull Request #18980 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[BrowserKit] Bump the dom-crawler minimum version requirement #18980

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

Conversation

jakzal
Copy link
Contributor
@jakzal jakzal commented Jun 6, 2016
Q A
Branch? 2.3
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #18826
License MIT
Doc PR -

The BrowserKit Client will not work with DomCrawler 2.0 if the CssSelector component is not installed.

This will require an amendment when merging into the 2.8 branch. It currently uses ~2.0,>=2.0.5|~3.0.0, while it should be ~2.1|~3.0.0.

@sstok
Copy link
Contributor
sstok commented Jun 6, 2016

@jakzal It seems your e-mail address is wrongly configured for Git, as your user linkage is broken for the commit.

@jakzal jakzal force-pushed the browserkit-dep-fix branch 2 times, most recently from 70a974d to 1215783 Compare June 6, 2016 12:57
    The BrowserKit Client will not work with DomCrawler 2.0 if the CssSelector component is not installed.
@jakzal
Copy link
Contributor Author
jakzal commented Jun 6, 2016

@sstok oops. Thanks for letting me know. Fixed now :)

@nicolas-grekas
Copy link
Member

2.3 is not maintained anymore :)

@jakzal
Copy link
Contributor Author
jakzal commented Jun 6, 2016

@nicolas-grekas Old habbits die hard ;)

This should be merged to 2.7, and the conflict on 2.8 should be resolved to ~2.1|~3.0.0.

@fabpot
Copy link
Member
fabpot commented Jun 6, 2016

Thank you @jakzal.

fabpot added a commit that referenced this pull request Jun 6, 2016
…ement (jakzal)

This PR was submitted for the 2.3 branch but it was merged into the 2.7 branch instead (closes #18980).

Discussion
----------

[BrowserKit] Bump the dom-crawler minimum version requirement

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

The BrowserKit Client will not work with DomCrawler 2.0 if the CssSelector component is not installed.

This will require an amendment when merging into the 2.8 branch. It currently uses `~2.0,>=2.0.5|~3.0.0`, while it should be `~2.1|~3.0.0`.

Commits
-------

5579d86 [BrowserKit] Bump dom-crawler minimum version requirement
@fabpot fabpot closed this Jun 6, 2016
@jakzal jakzal deleted the browserkit-dep-fix branch June 6, 2016 14:52
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
0