Please tag releases (e.g. major.minor.patch)
polyfractal opened this issue · 2 comments
Hi there =)
Would love it if you can tag releases, including patch updates, so that they are usable through Composer. As it stands, Analog's composer.json points to dev-master, which means it is automatically "dev" stability.
If a second library requires Analog, the end-user has to either specify 'dev' stability for all packages (not good), or specifically include Analog. Stability is not inherited (e.g. Library B which requires Analog cannot specify the stability), and so things break because everything is just thrown into dev-master.
Ultimately, this leads to composer files like this (where other/library requires Analog):
{
"require": {
"other/library" : "0.1.*",
"analog/analog": "dev-master"
}
}
When really it should just be:
{
"require": {
"other/library" : "0.1.*"
}
}
Thanks for pointing this out. Just made a small change and tagged it since I hadn't done so since before listing on Packagist. Cheers!
Thanks!