Skip to content

Version 0.6.0
Compare
Choose a tag to compare
@coenjacobs coenjacobs released this 17 Jan 16:13
· 123 commits to master since this release
0.6.0
ac3ff9e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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!

Assets 2
Loading