Releases and upgrading
Releases are published on GitHub with release notes describing what changed, and the extension is also listed on the Shopware Store.
Upgrading
If you installed with Composer:
composer update buckaroo/shopware6
bin/console plugin:update BuckarooPayments
bin/console cache:clearIf you installed from the Shopware Store, update through Extensions → My extensions.
Test an upgrade on a staging environment first, and read the release notes before you start. A release occasionally changes a default or retires a payment method, and it is easier to plan for that than to discover it afterwards.
There is no administration rebuild step. After updating, place a test payment to confirm the extension is working before you rely on it.
How releases are numbered
Buckaroo follows semantic versioning, so the version number tells you what to expect:
| Part | Means |
|---|---|
| Major | Breaking changes. Test carefully. |
| Minor | New functionality with limited impact. |
| Patch | Bug fixes and hotfixes only. |
The changelog and the releases page are the authoritative record of what changed. This page does not repeat them, because a copy would fall behind.
Reporting a problem
Report bugs and request features as issues on the repository. Include your Shopware version, your extension version, your PHP version, the relevant log lines and the transaction key.
For anything affecting live payments, contact support rather than opening an issue. See Contact us.
Found a security issue? Report it privately rather than opening a public issue. See Contact us.
Contributing
Contributions are welcome. Read the contributing guidelines before opening a pull request, and target the master branch.
Updated 6 days ago