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

Upgrade 2.0 from 1.0 #1199

Merged
merged 67 commits into from Aug 6, 2019
Merged

Upgrade 2.0 from 1.0 #1199

merged 67 commits into from Aug 6, 2019

Conversation

franmomu
Copy link
Contributor

@franmomu franmomu commented Aug 3, 2019

Q A
Branch? 2.0
Bug fix? yes
New feature? yes
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #1181, #1011
License MIT
Doc PR

I tried to merge 1.0 in 2.0 as in #1011 to bring back some lost commits

robfrawley and others added 30 commits May 21, 2017 16:31
Move to trusty for travis except for php 5.3
return filter function String
…m-allowed-failures

Remove Symfony 3.3 from allowed failures
…d-of-version-numbers

Use simplified Symfony version comparison operation and CS fixes
[Composer] Allow imagine-library version 0.7.0
- Allow construction of Locator without data roots for BC
- Mark FilesystemLocator::setOptions deprecated
Modify some PHP Annotations
Added support for centerright and centerleft position
Copy link
Member

@dbu dbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me. the lowest version build seems to be ending up with a too old version of the phpunit-bridge that loads the wrong phpunit. (i guess the problem is not related to this pull request)

@franmomu
Copy link
Contributor Author

franmomu commented Aug 5, 2019

It's fixed in the latest version of the library and as the docs says, it's not dependent on the project's symfony version:

The PHPUnit bridge is designed to work with all maintained versions of Symfony components, even across different major versions of them. You should always use its very latest stable major version to get the most accurate deprecation report.

So I increased the version to 4.2, what I'm not sure is if this should be done in another PR... 🤔

@dbu
Copy link
Member

dbu commented Aug 6, 2019

looks good to me, thanks!

@dbu dbu merged commit 715e567 into liip:2.0 Aug 6, 2019
@franmomu
Copy link
Contributor Author

franmomu commented Aug 6, 2019

you're welcome! should I do the same now merging 2.0 into master? so everything is in sync

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet