Closed derrabus closed 3 years ago
@derrabus I have deleted the outdated branch, can you let me know if the issue is fixed for you?
BTW i have released https://github.com/Masterminds/html5-php/releases/tag/2.7.5
I have deleted the outdated branch, can you let me know if the issue is fixed for you?
It is, thank you very much!
Hello ππ»
This repository has a
master
branch that is aliased for composer as2.7-dev
and a2.x
branch. This leads Composer (and thus Packagist as well) to believe, the 2.x branch is ahead of the master branch. You can see this on the packagist page of this package.The consequence is that if another project tries to install this package with
"masterminds/html5": "^2.7@dev"
or a similar constraint, Composer will pick the HEAD of the heavily outdated2.x
branch because2.x-dev
will always be considered to be ahead of2.7-dev
. This is what happens in Symfony's CI for instance.I don't know the reason for the current branching model, but my personal observation is that the
2.x
branch is obsolete andmaster
is where the magic happens at the moment. This does not match Composer's expectation of the branches.Because of that I'd like to suggest toβ¦
master
into2.x
regularlymaster
into2.x
once and switch development to the2.x
branch2.x
branch