Composer require minimum stability conflict.

[TheBabaYaga]

Hi,

Is there a reason why the minimum stability of the tagged versions is set to dev and not stable? We would like to include this library, but our minimum stability requirement is stable.

requires vgrem/php-spo dev-master#3318c782b8e1c1c1f274fb0bb37efab3a5274bee -> satisfiable by vgrem/php-spo[dev-master] but these conflict with your requirements or minimum-stability

Thanks in advance!

[vgrem]

Hi,

no any particular reason, just historically minimum-stability was set to dev.

Not sure, what would be the preferable option here, should we abandon minimum-stability attribute or replace its value to stable?

Vadim

[TheBabaYaga]

Hi,

It depends on the fact if your library depends on another library that isn't marked as stable.

From the composer docs:

minimum-stability (root-only)#
This defines the default behavior for filtering packages by stability. This defaults to stable, so if you rely on a dev package, you should specify it in your file to avoid surprises.

All versions of each package are checked for stability, and those that are less stable than the minimum-stability setting will be ignored when resolving your project dependencies. (Note that you can also specify stability requirements on a per-package basis using stability flags in the version constraints that you specify in a require block (see package links for more details).

Available options (in order of stability) are dev, alpha, beta, RC, and stable.