cweagans/composer-patches
Apply and manage patch files to Composer dependencies. Lets you keep fixes and tweaks outside vendor/ while still using normal Composer updates, with support for multiple patches per package, remote patch URLs, descriptions, and CI-friendly installs.
patch by @afilina in https://github.com/cweagans/composer-patches/pull/379Full Changelog: https://github.com/cweagans/composer-patches/compare/1.7.3...2.0.0
Full Changelog: https://github.com/cweagans/composer-patches/compare/2.0.0-beta1...2.0.0-beta2
A lot of work went into this release. Below are all of the PRs that went into this release, but it might be more straightforward to read the new documentation. The 2.0.0 release will definitely work a little differently than you're used to if you've been using the 1.x releases.
patch by @afilina in https://github.com/cweagans/composer-patches/pull/379Full Changelog: https://github.com/cweagans/composer-patches/compare/1.6.0...2.0.0-beta1
Full Changelog: https://github.com/cweagans/composer-patches/compare/1.7.2...1.7.3
This release resolves a compatibility problem with 2.1 where packages would be deleted and not reinstalled during patching. Thanks to @Seldaek for the resolution on both the 1.x and master branches!
Changes since 1.7.0:
Retry failed downloads to work around some Drupal.org infrastructure hiccups
Thanks @danepowell!
Two critical bugfixes are included in this release:
1.6.0 fixes a few bugs, adds some features, and resolves a regression with applying patches that are in a separate patches file.
Includes fix for #36 (Dependencies' patches are ignored if the root package does not define any)
How can I help you explore Laravel packages today?