Ship Magento upgrades without missing a single customisation

One Docker command tells you exactly which of your overridden files changed in Magento core, before you commit the upgrade.

docker run --rm -v $(pwd):/project:ro samjuk/magento2-upgrade-patch-helper:8.2 Read the docs on GitHub

A Dockerised wrapper around the Ampersand Magento 2 Upgrade Patch Helper. Runs anywhere Docker does, including CI.

upgrade-patch-helper --branch origin/master 3 files need attention

Observer/CheckoutObserver.php	core file changed	review
templates/cart/item/default.phtml	core file changed	review
Plugin/ProductPlugin.php	core file changed	review
Helper/Data.php	core file unchanged	ok

Example output comparing every overridden file against the target Magento version, before you commit the upgrade.

1 Docker command, no host PHP setup

0 files written into your project

Any CI runner with Docker available

How it works

1

Update composer.json to your target Magento version

Run composer update to pull in the new version and resolve any dependency conflicts. Do not commit yet, because the tool compares your working tree.

Run one Docker command from your project root

Mount your project directory and let the tool compare your overrides against the core diff between versions.

docker run --rm \
    -v $(pwd):/project:ro \
    -v $(pwd)/upgrade-output:/output \
    -v ~/.composer/cache:/root/.composer/cache \
    -v ~/.composer/auth.json:/root/.composer/auth.json:ro \
    samjuk/magento2-upgrade-patch-helper:8.2 \
    --branch origin/master

3

Review the report and action flagged files

The output lists every overridden file that changed in Magento core between the two versions. Work through each one before committing your upgrade.

Common questions

Does this work with any Magento 2 version?

Yes, it supports any Magento 2.x version pair. Pass your target version as an environment variable and the tool handles the diff automatically.

Does it need Docker Desktop, or will a Linux CI runner work?

Both work. It runs in any Docker environment: local Docker Desktop, Docker on Linux, or any CI runner with Docker support (GitHub Actions, Bitbucket Pipelines, etc.).

Will it modify my project files?

No. The tool is strictly read-only. It mounts your project as a volume and generates a report, but never writes back to your working directory (unless you mount the output folder into your working directory).

What is the difference between this and running the original patch helper?

Nothing. Apart from being a simpler interface (single docker command), and having the tool run isolated from your environment.

Ship Magento upgrades without missing a single customisation

How it works

Update composer.json to your target Magento version

Run one Docker command from your project root

Review the report and action flagged files

Common questions

No setup. One command. Know before you commit.