It would be great if one could specify for example ^5.3 before it is released and point it against the master branch using Composer's branch alias feature.
This way developers may use the master branch as 5.3 until the 5.3 tag has been released. When the stable version of 5.3 has been released, Composer will use that tag instead.
It is done by specifying a branch-alias field under extra in the composer.json file:
I would gladly open a pull request adding this feature but I need some guidance. I'm guessing this could be added via the johnpbloch/build-wp repository?
It would be great if one could specify for example
^5.3
before it is released and point it against the master branch using Composer's branch alias feature.This way developers may use the master branch as
5.3
until the5.3
tag has been released. When the stable version of5.3
has been released, Composer will use that tag instead.It is done by specifying a
branch-alias
field underextra
in thecomposer.json
file:I would gladly open a pull request adding this feature but I need some guidance. I'm guessing this could be added via the
johnpbloch/build-wp
repository?