Releases and upgrading
How we version the plugin, how long each version is supported, and how to upgrade safely.
Versioning
The plugin follows semantic versioning: MAJOR.MINOR.PATCH.
| Meaning | What to do | |
|---|---|---|
| MAJOR | Breaking changes | Read the release notes. Test thoroughly on staging. Budget time for it. |
| MINOR | New features and payment methods, backwards compatible | Safe to apply after a staging check. |
| PATCH | Bug fixes and security fixes only | Apply promptly. |
Release notes
The full changelog lives on GitHub: buckaroo-it/Magento2/releases.
Read the notes for every version between your current one and your target, not just the target. A breaking change three releases back still affects you.
Get notified of new releases
The quickest way to hear about a new version is to subscribe on GitHub:
- Open the Magento 2 repository.
- Select Watch, then Custom.
- Tick Releases and save.
You'll then get an email whenever we publish a release, without the noise of every issue and pull request.
Star the repository too if you find it useful. Starring is a bookmark rather than a subscription, so it won't notify you on its own, but it helps other merchants find the plugin.
You can also subscribe to the Buckaroo status page for incidents and maintenance, which is separate from plugin releases.
Magento compatibility
We aim to support the three most recent Magento releases. At the moment that means:
| Magento / Adobe Commerce | 2.4.7 – 2.4.9 |
| PHP | 8.1 – 8.5 |
When Adobe releases a new version, support moves forward with it and the oldest of the three drops off. There's no fixed end-of-life date attached to any particular plugin version; the window simply follows Magento's own release cadence.
Check compatibility before you upgrade Magento, not after. The plugin version you're running may not yet support a newer Magento release, and upgrading Magento first can leave your checkout broken while you wait.
On a Magento release older than the three supported, the plugin may still work, but it isn't tested against those versions and new payment methods may not behave as expected.
How to upgrade
Minor and patch releases
Run the following from your Magento root directory:
composer update buckaroo/magento2
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento cache:flushMajor releases
- Read every release note between your version and the target.
- Take a full backup of both the database and files.
- Upgrade on staging first.
- Run through the test scenarios in Test and go live.
- Check any customisations you've made against the changed code.
- Schedule the production upgrade outside peak hours.
Pinning a version
To install or move to a specific version rather than the latest:
composer require buckaroo/magento2:^2.0
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento cache:flushPin only when you have a specific reason to. A pinned version won't pick up new releases, including security fixes, until you change it.
Contributing
The plugin is open source. Bug reports, feature requests and pull requests are welcome. See the contribution guidelines. Target the develop branch when opening a pull request.
Security issues should be reported privately. See SECURITY.md rather than opening a public issue.
Updated 3 days ago