NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #2611 most downloaded on Packagist
Applies a patch from a local or remote file to any package that is part of a given composer project. Patches can be defined both on project and on package level. Optional support for patch versioning, sequencing, custom patch applier configuration and patch command for testing/troubleshooting added patches.
Latest stable
6.1.0
Last release 1 months ago
14 Oct 2026
Release timing varies
gaps range from 2 weeks to 12 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
212 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
all features and fixes in this release are forward-ported from 3.44.0
all features and fixes in this release are forward-ported from 3.43.0
all features and fixes in this release are forward-ported from 3.43.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
https://github.com/vaimo/composer-patches/blob/master/CHANGELOG.md#4110
https://github.com/vaimo/composer-patches/blob/master/CHANGELOG.md#4110
all features and fixes in this release are forward-ported from 3.42.0, 3.42.1 & 3.42.2
forward-port (3.41.0): allow patcher config overrides per package instead of allowing it only per patch definition (reserved key: '_config'). More on
forward-port (3.40.0): allow patch to target the autoloader root (instead of targeting package root) by configuring 'cwd' key to 'autoload'
follow-up to incorrectly released version (4.8.1); no extra changes done
forward-port (3.39.1): patches not applied when dealing with requires that use dev branches (even when version available in package config or when dev
all features and fixes in this release are forward-ported from 3.39.0
all features and fixes in this release are forward-ported from 3.39.0
forward-port (3.38.0): hide all information on previously applied patches by default (when patches for certain package are re-applied) and only show t
forward-port (3.37.1): some patches that patched multiple files applied only half-way through on certain OS's without returning with proper exit code
This release addresses some issues that could be encountered when using embedded version constraints for bundled patches. Additionally the patch listi
This release addresses some issues that could be encountered when using embedded version constraints for bundled patches. Additionally the patch listing command was improved to allow listing of absolutely every patch that's declared (with additional status indicator).
All changes in this release forward-ported from 3.37.0
Addresses some issues that one would encounter when trying to declare a bundled patch with embedded target info declaration. Usage simplified.
Addresses some issues that one would encounter when trying to declare a bundled patch with embedded target info declaration. Usage simplified.
All changes in release forward-ported from 3.36.0
Provides a solution/support for the contents of older composer.lock files where the plugin used to inject a "patches_applied: true" value which it no
Provides a solution/support for the contents of older composer.lock files where the plugin used to inject a "patches_applied: true" value which it no longer does (nor does the plugin now allow the value of given extra data key to be anything other than an array).
This release introduces much more graceful manner of sanitizing composer.lock after the process of applying patches has been finished.
This release introduces much more graceful manner of sanitizing composer.lock after the process of applying patches has been finished.
Potential issues with the code that deals with rewriting the lock file. Logic changed to embrace the internal package resolver logic of Composer rathe
Potential issues with the code that deals with rewriting the lock file. Logic changed to embrace the internal package resolver logic of Composer rather than assuming that every lock record matches directly name-to-name. Forward-ported from 3.35.1.
Addresses some issues with 'undo' and 'redo' commands where certain sequences produce results that are not consistent with the semantic meaning of the
Addresses some issues with 'undo' and 'redo' commands where certain sequences produce results that are not consistent with the semantic meaning of the commands.
All changes introduced (and forward ported over) in 3.35.0
Fixes module behaviour for certain project states where different commands are used in certain sequence - resulting a situation where full 'reapply' w
Fixes module behaviour for certain project states where different commands are used in certain sequence - resulting a situation where full 'reapply' was needed to be able to continue.
Also introduced: level and category (latter is not yet used for anything) tags for embedded target info.
forward-port (3.33.1): improved error reporting when encountering issues on composer lock cleanup
Introduces new feature of allowing patch to be applied to project root or to vendor root when certain special case calls for it.
Introduces new feature of allowing patch to be applied to project root or to vendor root when certain special case calls for it.
definition list validation command returning with false failures when using #skip on patch paths
forward-port(3.32.0): allow comments on any level and with any keyword as long as it starts with underscore (_)
This release changes the default behaviour of the module and removed bunch of old environment values that were introduced before 'composer patch' comm
This release changes the default behaviour of the module and removed bunch of old environment values that were introduced before 'composer patch' command was available.
Bundle patches that touch several packages were applied in the order of the first target group they appear in instead of the resolved (declared / @aft
Full Changelog: https://github.com/vaimo/composer-patches/compare/3.53.5...3.54.0
Merge pull request #168 from vaimo/feature/applicable-variable-in-pat…
Merge pull request #168 from vaimo/feature/applicable-variable-in-pat…
bundled patches fail to apply when using patch-mapping configuration due to refactored code in 3.53.2 having messed up argument order used for a sub-f
patch applier crash when branch alias defined for root package (scenario: root-branch-alias) [pull/73]
patches applied before packages properly re-installed with Composer V2 (missed the fact that installations, like downloads are now done in asynchronou
minor issue addressed with V2-style call being in code without version-check (said call is currently backwards-compatible with V1, but you never know
add support for Composer 2 [issues/59]
remove patch availability validation crash under certain package setups
allow global usage of the plugin when explicitly enabled via environment variable: COMPOSER_PATCHER_ALLOW_GLOBAL_USAGE (pull/45)
some errors not properly reported in the 'most likely' errors brief report (for patches with corrupt content)
allow the plugin to be installed as dependency to globally installed package (as part of dependency of some global package); previously caused every c
allow defining OS-specific applier operation without overwriting the default operation value
running 'composer update --lock' not cleaning up composer.lock afterwards when patches already applied. No such issue when no patches applied at all (
loosened dependency on drupol/phposinfo to make sure that the module is installable on all PHP version (latest release of the module is only covering
the command patch:list not usable when some patch configuration included remote patches that would have resulted in 404 errors on apply (now listing s
allow defining sha1 checksum for remote patches through 'sha1' key within JSON definition
needless whitespace in output when using patches-search (extra line for patch label added for no reason)
package configuration and build flow updates
### Maintenance * code quality improvements Links: src diff
allow very precise configuration for specific OS based on OS names in drupol\phposinfo\Enum\OsName
more clear error reporting when encountering patch reversals (failures from log output analysis)
certain behaviour flags incorrectly forced to false (explicit flag) when using redo/undo with no option to override said falsey value
patches validation not failing when there are patch files present without patch target definition in JSON files and using sym-linked patch folder (not
using printf variable syntax in patch descriptions crashed the patch applier
the meta-data @skip tag not perceived properly (this actually affected all tags that had no value)
basePatch templates not being applied after code changes from last release
patch file meta-tags conflict in situations where there are values for all of: depends, package, version; the following setup now results in package+v
patch file meta-tags overwriting each-other rather than stacking (when, say @depends is used multiple times)
added notice to the 'most likely error' output (on patch failure) to indicate that the list presented is not the full list of details
broken compatibility with PHP 5.3 (wrong array syntax used)
highlight most probable error that caused patch to fail in the non-verbose error message (full logs available when running with -vvv); this change was
support for older (<1.1) Composer releases faultily implemented where the availability with CommandsProvider was incorrectly checked for
wrong path used for pre-loading classes while running composer commands when the plugin package used as ROOT
allow platform requirement dependencies on patches a'la php:>=7.2 (previously only package dependencies could be declared); usable with "depends" conf
This release comes basically with re-written logic to the core of the patch apply queue generation due to issues with the old logic. The listing comma
This release comes basically with re-written logic to the core of the patch apply queue generation due to issues with the old logic. The listing command now also uses same code which removes some of the confusion when using apply and seeing something different than what list reports
allow patch:validate to use only patches that the root package owns: --local
Allow declaration of pathces that only apply when owner package is used as ROOT package (README/Patches: local patch)
allow patch file paths, etc to be defined under extra/patcher key to make sure that they don't hog up too much main level keys of 'extra' config for g
One column per quarter.