NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #2480 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.
https://github.com/vaimo/composer-patches/blob/master/CHANGELOG.md#3422-2019-03-21
https://github.com/vaimo/composer-patches/blob/master/CHANGELOG.md#3422-2019-03-21
Your coding agent can read these notes before it upgrades. Set up the MCP server →
added more informative patches configuration JSON validation (that gives exact details on what's wrong with the JSON file)
allow patcher config overrides per package instead of allowing it only per patch definition (reserved key: '_config'). More on this under the topic of
allow patch to target the autoloader root (instead of targeting package root) by configuring 'cwd' key to 'autoload'
follow-up to incorrectly released version (3.39.1); no extra changes done
patches not applied when dealing with requires that use dev branches (even when version available in package config or when dev branch aliased as prop
added --brief to list command (skips over description, etc)
hide all information on previously applied patches by default (when patches for certain package are re-applied) and only show the ones that changed, a
some patches that patched multiple files applied only half-way through on certain OS's without returning with proper exit code on failure (or failed h
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).
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.
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.
conflicting project applied patches state when doing a --no-dev call and a filtered undo/redo after that
allow patch path strip level to be defined in patch's embedded target-info declaration (@level )
improved error reporting when encountering issues on composer lock cleanup
allow patch applied root to be configured per patch to allow patching of files that are mapped by other composer plugins to project root (see more at
definition list validation command returning with false failures when using #skip on patch paths
allow comments on any level and with any keyword as long as it starts with underscore (_)
This release introduces additional mechanism of halting the process of applying patches when targeted package has local changes. Previous release just
This release introduces additional mechanism of halting the process of applying patches when targeted package has local changes. Previous release just re-installed the package without prompting nor warning the user.
New standard behaviour is to STOP, when this is encountered to avoid potentially wiping out someone's work.
patch apply failure on fresh projects under certain conditions when loading the 'patches-applied' from .lock file (which in-between the run is set to
Giving users the option to single out certain embedded-info patches as development-only patches by adding @type tag to them with the value of "dev" or
Giving users the option to single out certain embedded-info patches as development-only patches by adding @type tag to them with the value of "dev" or "development".
Also includes fixes to doing partial forced re-apply (with redo) and improvements on handing bundled patches when using the before-mentioned command.
The command was not usable in non-root package context when the package owned bundle patches
The command was not usable in non-root package context when the package owned bundle patches
Introduces new function that allows developers to double-check that they did not forget to add any of the patch target information in JSON files after
Introduces new function that allows developers to double-check that they did not forget to add any of the patch target information in JSON files after including a certain path to the patch owner package. Also includes several new aliases for embedded targeting info and better sub-command support for 'patch' command that used to have way too much responsibility.
Major step towards getting rid of forcing user to declare information twice.
Major step towards getting rid of forcing user to declare information twice.
Allow users to provide a root folder for where their patches live and resolve the targets from the data that is provided within the patch itself (special tags in the patch header).
allow patches information to be extracted from the patch file (see: patch declaration with embedded meta-data)
allow multiple 'patches-depend' declarations for different kind of patches (bundle VS normal patch)
allow multiple patch-base's to be defined based on vendor or full package name
### Fix * missing file added Links: src diff
array-based values ended up being treated as version constraints (issue with label-version exploder)
label-version definition exploder not handling a list of multiple versions correctly
new definition format that consists of description/filename and version restriction
### Maintenance * debug code removed (shame!) Links: src diff
allow patch base path variables to have partial value extractors defined against them
wrong error message when bundle patch is not found from defined path
minor modifications to patch filtering logic
fix to a crash that happened when resetting targets that relate to bundle patches
minor change to constant naming to make it match up with patch command. COMPOSER_PATCHES_PREFER_OWNER renamed to COMPOSER_PATCHES_FROM_SOURCE. Backwar
bundled patches reset mechanism targeting wrong packages (where root package as owner was being sent to 'patches reset' which caused a crash)
allow default indirect dependency to be defined for a package version restriction
package meta-data fixes. syntax error in composer.json
bundled patch targets resolver failing due to patch info loaders being re-arranged and certain array values no longer being available (patch path not
minor architecture changes around filtering patch files / packages
allow patch exclusions based on partial paths
patcher configuration overrides that depend on the OS
make it possible to allow patch download from HTTP (separate config from allowing this for packages)
re-apply remote patch when it's contents have changed (download remote patches beforehand and make the decision based on the contents of the patch)
documentation re-organized and simplified
minor readme and package description updates
documentation changes. Some explanations re-written. Added example for bundle-patch
documentation re-organized to prioritize quick comprehension on the basics of the module's functionality
added new operation to check if applier is available (can be used to exclude certain appliers on certain systems)
several config keys renamed (patchers => appliers, patcher-config => patcher). Backwards compatible
switched to using PHP constants for OS-related values like newline and path separator
patches not registered for patch target packages when 'COMPOSER_PATCHES_FATAL_FAIL' enabled and error is encountered
composer patch command option 'undo' not working correctly when patching explicitly set to be enabled in composer.json of the project
don't force bundle patches to have 'vendor' in their paths as it's a customizable value
One column per quarter.