Please kindly squash your commits together. If you don't, we'll try to remember to do it for you but it's best if you save us this trouble.

How to do that?

1. git rebase -i origin/1.12.x, assuming origin is a git remote that points to this repository, and not your fork. If you're not sure what your remotes are, run git remote -vvv, there should be your fork and the holy/reference/base/origin/whatever-you-call-it repository.
2. A window will show up with many lines, replace pick with fixup on every line but the first one
3. Close your editor, git should do its magic, and you should end up with one commit
4. Use git push --force to overwrite what you already push. Don't forget the --force option otherwise git will try to merge both things together.

@dmaicher build is failing due to a deprecation in the 4.4 job. Do you want to take a look at that in a separate PR? Otherwise I'll do so in the afternoon.

@dmaicher build is failing due to a deprecation in the 4.4 job. Do you want to take a look at that in a separate PR? Otherwise I'll do so in the afternoon.

@alcaeus yeah I also saw it. Not sure I have time for it today 😢

Don't worry: #1075. Just need to rebase :)

Thanks David!

Here is the recipe change: symfony/recipes#695

@alcaeus @greg0ire @nicolas-grekas when we release this it will possibly cause some issues for users that don't also sync the latest recipe change (symfony/recipes#695)

It will leave them without proper caching for prod environments 😢 Not sure how we can avoid this though...

But maybe chances are high that new projects started with fresh 1.12/2.0 recipes are not running in production yet? 😄 🙈

I think we cannot avoid it, but before it was an implicit dep on my project, so I ended up automatically using 2.0 via composer update. I had to manually require 1.x. But nevermind we need to fix it and help the Community to get a working state back again 👍🏻

Fixing this is not a question of if, but how. The current upgrade path may cause some pain for people in production if they don't upgrade their flex recipes or don't update their config manually, but I believe we can account for that by communicating the change appropriately.