nevvermind eb2aa14830 Make plugins have actual constraints instead of fixed versions ... Instead of developing plugins against a single, fixed Plugin API version - `"composer-plugin-api": "1.0.0"`, this change will allow plugin developers to use versions like `"composer-plugin-api": "~1.1"` or `"composer-plugin-api": ">=2.1 <3.0"`, aka actual Composer-compatible constraints. Only the "1.0", "1.0.0" and "1.0.0" Plugin API versions will be regarded as BC versions, and internally converted to "^1.0"; every other declared version string will be kept as it is. Because of this new constraint flexibility, plugin version mismatches will be skipped, which means those plugin will NOT be registered to the system. Previously, a mismatch triggered a warning, but plugins were still registered.		2015-06-02 14:10:09 +01:00
..
Archiver	Config Git repository user	2015-02-16 11:55:56 -04:00
Dumper	Use https where possible	2015-05-04 19:37:57 +02:00
LinkConstraint	Only compare branches as versions in the policy to sort packages, but not in the solver, fixes #1817	2013-05-23 18:12:54 +02:00
Loader	Use https where possible	2015-05-04 19:37:57 +02:00
Version	Make plugins have actual constraints instead of fixed versions	2015-06-02 14:10:09 +01:00
BasePackageTest.php	Fixed typos	2013-12-27 11:51:01 +00:00
CompletePackageTest.php	Add parallel build to travis script	2013-09-25 10:23:48 +02:00
LockerTest.php	Use https where possible	2015-05-04 19:37:57 +02:00