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.
auto-resolve bundle patch targets when 'targets' not defined
allow multiple patch files to be defined to enable high-level patch grouping (or to allow occasional cleanup where really old legacy patches could be
Your coding agent can read these notes before it upgrades. Set up the MCP server →
crash when trying to declare path stripping level for version-branched sources
allow certain patches to be processed only with very strict path strip options and patcher type
updated lock to latest due to composer validate error
roll-back with 'undo' to reset package when used with specific targets
option to apply only some of the patches based on text-based file name filter
introduced a new composer command to make it easier to re-apply all patches and give newly defined patches a quick test-run (composer patch)
reset all patched packages when vaimo/composer-patches in removed from a project (with an option of leaving the patches applied)
### Fix * changes to package meta-data Links: src diff
declaration of 'depends' was overriding 'version'. Constraints defined on those keys are now merged
### Maintenance * changes to package metadata Links: src diff
added new environment flag to force patcher to extract the patch info from vendor folder instead of using the information from installed.json (mainly
process every source path and check for 'skip' flag. In certain cases, the source-path flag was ignored
allow patches to be skipped by adding 'skip' flag in it's definition (good as maintenance flags when doing major base-framework upgrades)
code cleanup (some debugging code removed)
added version branching for sequenced items
allow multiple patch files to be declared under same label (see: Version branching)
make sure that path normalizer does not touch root-level patch declarations
make sure that 'resetting patched package' is not shown when package is indirectly targeted
allow bundled patches (that target multiple packages) to be declared, tracked, reverted correctly when changed or removed (see: Bundled patches)
Nothing published for this version
Nothing published for this version
Nothing published for this version
allow dev-only patches to be declared (see: Development patches)
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.