Update branch alias

[driesvints]

My build for Horizon with Symfony 5 support was failing because Composer believes atm that 5.0.x-dev targets the 4.x branch because of the current branch alias.

https://travis-ci.org/laravel/horizon/jobs/616761151

I've updated it to the correct branch alias as well by setting it to 4.x-dev because that's the proper notation. Otherwise Composer believes this branch only holds patch releases. We did the same change for the framework and we're also rolling it out on the other first party libraries.

testbench-core also needs to be updated with this as well as both master branches of the repos: https://github.com/orchestral/testbench-core/blob/4.x/composer.json#L47

[crynobone]

I think you need to update your .travis.yml and remove Laravel 6.

As for Laravel 7, it related to deprecated class in Laravel.

[driesvints]

@crynobone you're correct! Thanks for spotting that.

Nevertheless this should definitely be merged as well as the other notes I mentioned. I'm not sure why you believe this PR shouldn't be merged?

[crynobone]

I'm not sure why you believe this PR shouldn't be merged?

As far as I know, there no affect since master branch composer.json will override any other branch aliasing.

[driesvints]

@crynobone this is for the 4.x branch.

[crynobone]

Yes, because master branch will override everything else. I can put "dev-master": "3.x-dev" in 4.x branch and packagist still ignored it.

---

The alias must be a comparable dev version, and the branch-alias must be present on the branch that it references. For dev-master, you need to commit it on the master branch.

https://getcomposer.org/doc/articles/aliases.md#branch-alias

[driesvints]

@crynobone okay, I just thought you wanted to fix this because it's a bit weird to see the 5.0 alias on the 4.x branch but your call :)

[crynobone]

Nah, I be wasting time updating all the branches that I maintain just for this every 6 months.