Hello 👋🏻

This repository has a master branch that is aliased for composer as 2.7-dev and a 2.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 outdated 2.x branch because 2.x-dev will always be considered to be ahead of 2.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 and master 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…

• either merge master into 2.x regularly
• or merge master into 2.x once and switch development to the 2.x branch
• or delete the 2.x branch