Releases: Ocramius/PackageVersions
1.1.3
This release fixes a bug that caused PackageVersions to prevent
the composer remove and composer update commands to fail when
this package is removed.
In addition to that, mutation testing has been added to the suite,
ensuring that the package is accurately and extensively tested.
Total issues resolved: 3
1.1.2
This release fixes a bug that caused PackageVersions to be enabled
even when it was part of a globally installed package.
Total issues resolved: 3
1.1.1
This release removes the "files" directive from
composer.json,
as it is no longer needed for composer install --classmap-authoritative.
Also, that directive was causing issues with HHVM installations, since
PackageVersions is not compatible with it.
Total issues resolved: 1
1.1.0
This release introduces support for running composer install --classmap-authoritative
and composer install --no-scripts. Please note that performance
while using these modes may be degraded, but the package will
still work.
Additionally, the package was tuned to prevent the plugin from
running twice at installation.
Total issues resolved: 10
- 18: Fails when using composer install --no-scripts
- 20: CS (spacing)
- 22: Document the way the require-dev section is treated
- 23: Underline that composer.lock is used as source of information
- 27: Fix incompatibility with --classmap-authoritative
- 29: mention optimize-autoloader composer.json config option in README
- 30: The version class is generated twice during composer update
- 31: Remove double registration of the event listeners
- 32: Update the usage of mock APIs to use the new API
- 33: Fix for #18 - support running with --no-scripts flag
1.0.4
This release includes a fix/workaround for composer/composer#5237, which causes ocramius/package-versions to sometimes generate a Versions class with malformed name (something like Versions_composer_tmp0) when running composer require <package-name>.
Total issues resolved: 2
1.0.3
This release fixes an issue related to concurrent autoloader re-generation caused by multiple composer plugins being installed. The issue was solved by removing autoloader re-generation from this package, but it may still affect other packages.
It is now recommended that you run composer dump-autoload --optimize after installation when using this particular package.
Please note that composer (install|update) -o is not sufficient to avoid autoload overhead when using this particular package.
Total issues resolved: 1
1.0.2
This release fixes issues related to installing the component without
any dev dependencies or with packages that don't have a source or dist
reference, which is usual with packages defined directly in the
composer.json.
Total issues resolved: 3
1.0.1
This release fixes an issue related with composer updates to already installed versions. Using composer require within a package that already used ocramius/package-versions caused the installation to be unable to write the PackageVersions\Versions class to a file.
Total issues resolved: 6
- 2: remove unused use statement
- 3: Remove useless files from dist package
- 5: failed to open stream: phar error: write operations disabled by the php.ini setting phar.readonly
- 6: Fix/#5 use composer vendor dir
- 7: Hotfix - #5 generate package versions also when in phar context
- 8: Versions class should be ignored by VCS, as it is an install-time artifact
