Closed aik099 closed 9 years ago
Thanks. I'm updating the documentation to include CompletionAwareInterface
at the moment, then I'm planning to release 0.5.0. The docs on composer branch-alias aren't entirely clear, but it seems like 0.4.x-dev
is too specific and will stop working with this new release. Do you know if changing that to 0.x-dev
will work (I'll test it out before pushing in any case)?
It's designed to specify current feature version that maps to the branch. I usually increment the branch alias before I'm planning to make a release with new features.
This way on packagist's library page people will see both 0.4.x-dev
and 0.5.x-dev
aliases and their old dependencies will still work, but be locked to last commit on master
branch that was made before alias was changed.
Ok thanks, I'll do that then.
With branch alias specified it's now possible to use library with
~0.4@dev
version constrain, which will usemaster
branch unless project stability is forced to stable.More info at https://getcomposer.org/doc/articles/aliases.md .