Release 0.7.1

As @szepeviktor mentioned, the PHAR we created starting from the last release was way too big (at a whopping 14MB). This was caused because all the development dependencies were included as well. This release changes that, reducing the created PHAR to 1.3MB.

Release 0.7.0

This release quickly follows the 0.6.0 release and is focussed on solving the problems with distribution and isolation Mozart has been facing. That's why Mozart is now available as a Docker image and a PHAR file will be attached to each release and can be downloaded from the releases page (or via Phive). All of this is to ensure that Mozart can run in isolation itself and not have potential conflicts with your projects dependencies (yes, for a package claiming to solve dependency conflicts, this is crazy meta - I know!).

I've also put lots of attention to the installation instructions in the README, explaining how the different installations methods work and point at the pros and cons for each.

Mozart is now supporting all supported PHP versions, which include: PHP 7.3, 7.4 and 8.0. Support for PHP 7.2 has been dropped.

Other than the logistical part of the project, 0.7.0 is a very small release. No actual code has been changed, apart from some code standards and minor fixes. The availability of the Docker image and the building of PHAR files is a big step forward though!

Version 0.6.0

This has been in the works for far longer than it should have. Special thanks to @BrianHenryIE as he has been so hard at work with multiple changes and debugging things for other developers, in the issues. I try to scrape every single bit of time that I can put into Mozart, but I don't know how I could do it without him. 🎉

In this release, the highlights are:

• Default to handle all packages required by your project: If you want all your packages required in your project, to be transformed by Mozart after installing, you can omit the packages key in the configuration and Mozart will transform all packages.
• The autoload configuration of a package can be changed: Using the override_autoload configuration key, you can specify the autoload configuration for that package, after it is transformed by Mozart.
• You can now exclude packages that are being loaded from one of your own dependencies: Using the excluded_packages configuration key you can disable a package from being transformed by Mozart. This is useful for packages, for example PSR-11's ContainerInterface that is a standardised class.
• The full dependency tree of packages is now properly being transformed: This means that the full tree of dependencies is processed, no matter how deep that tree is.

Besides the highlights, Mozart has been improved across the board. A whole lot of fixes have been merged over the past couple months, that have made the code base more solid and bug free.

Aside: By the end of last year, I posted a long post about my thoughts about the future of Mozart: The future of Mozart - we're at a crossroad! - I've spent the first weeks of this year, thinking this through some more. Right now, I feel I have a solid understanding of the most pressing issues within our tiny ecosystem. Enough at least, to put a little roadmap together, which I'll post soon. The next release of Mozart will be all about distribution of the package, adding a Docker image and possibly other means of running the code, in addition to requiring Mozart as a package in your project. More on that soon!

0.6.0 Beta 3

• Conditional logic in verifying the composer.json file is valid #49
• Classmap target directory will include a .gitkeep file in order to persist the directory in CVS #52
• Classmap replace is done on the full copied classmap directory structure #42

Thank you @markjaquith and @BrianHenryIE for your contributions! 🎉

0.6.0 Beta 2

Second beta today, but I have messed up something while reviewing and that is now fixed.

0.6.0 Beta 1

With so much going on, I feel a proper beta for this next release is in order. I'd like to run this through some rigorous testing before tagging the stable release.

I still want to check if #42 is still required after #39 is already merged.

Thanks a ton, @BrianHenryIE for all the help and contributions. I'll get your contributions properly attributed in the release notes once this becomes the next stable.

Version 0.5.1

Fixed: Symfony command must have an integer as return status code (#33)

Version 0.5.0

Santa came early and dropped a new release of Mozart. This release contains:

• Thanks to @Willemijnr, I have been able to find this bug. More details in pull request #31, but the tldr is: After moving packages to the target directory, they are removed from the /vendor directory. This has been on my radar for a while to test out, but this bug proved that it was worth my while.
• In #32 I have bumped all requirements to a more modern version. This includes PHP 7.2 because PHP 7.1 is now EOL for almost a month. My personal opinion is still that Mozart is a developers tool and developers should lead by example: Hello to a more modern PHP version! 🎉

Version 0.4.0

Version 0.4.0 of Mozart is here. The main change that everyone will notice is that Mozart now requires PHP 7.1 and up. The reasoning behind this is documented in #26, but the tldr is:

Mozart is a developers tool. In my humble opinion, developers should lead by example in using supported PHP versions only and have no reason to stay behind on unsupported versions.

Further changes in this release:

• Thanks to @kmgalanakis, we now have full Windows support, resolving an issue with the directory separator symbol. See #21 for more details.
• Thanks to @schlessera, we're now using modern versions of the Symfony components being used. With bumping the PHP version requirement, allowed me to make these new versions the only version we're using and making the version constraint more specific (only allowing ^4 now of both symfony/console and symfony/finder packages). See #25 for more details.
• I've fixed a bug where it would fail previously when trying to copy the same package to the new directory more than once. See #19 for more details.

Big thank you to everyone contributing to and using Mozart, your help is very much appreciated! 🎉

0.3.0 ready for testing!

Thanks to the hard work of @costasovo in his attempt to support rewriting the full dependency tree in #10, I have been able to tackle this issue now finally. This release contains:

• Full dependency tree support. All dependencies (and their dependencies and so on...) are now automatically processed by Mozart. You only need to define the dependencies of your own project that you want to rewrite and the full dependency tree of those packages will be processed.
• Smarter logic when copying classmap autoloaders. Sometimes there was weird behaviour noticeable when a package contained both classmap autoloaders and namespace autoloaders, resulting in files not being copied or ending up in the wrong directories. This release fixes that.