Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Drop version constraint to allow future package releases (or abandon package) #22
I can immagine that this is going to be a bit controversial, but I'm not sure if this package was a good idea.
When users use
When doctrine/doctrine-migrations-bundle 3.0 will be released (or orm 3.0 or dbal 2.0), the only way to allow the upgrade it is to allow it in this package, as example defining
But since that was a minor/bigfix release, any user that had installed
My proposal to remove the version constraint has the same disadvantages, but does not oblige the doctrine team to keep updated this repo each time there is a major release on doctrine.
Another solution is that each time a major release is added in the constraints, this package should release a major release, in this way we avoid delivering unexpected major releases. Similar as #18
A third solution (that does not exclude the previous one) is to deprecate this package and let users install what do they need.
After update, I can't run console, get some errors. I tried to use add these packages explicitly with old versions and it started to work