Shopware changed their store API to require a different sequence of requests when uploading a new binary or replacing an existing binary.
Old sequence:
Upload the plugin .zip file to create a new binary entity.
Set version, changelog, compatible Shopware versions and options on the binary received in 1.
Save the modified binary.
New sequence:
Validate the plugin .zip file (only when creating a new version).
Create a new binary with version, changelog and compatible Shopware versions (only when creating a new version).
Upload the plugin .zip file for the new or existing binary.
Update version, changelog, compatible Shopware versions and options of the new or existing binary again.
Since Shopware stopped supporting ionCube encryption (it is no longer offered when creating a release via their account UI) I also deprecate the respective command option with this PR.
Shopware changed their store API to require a different sequence of requests when uploading a new binary or replacing an existing binary.
Old sequence:
binary
entity.binary
received in 1.binary
.New sequence:
binary
with version, changelog and compatible Shopware versions (only when creating a new version).binary
.binary
again.Since Shopware stopped supporting ionCube encryption (it is no longer offered when creating a release via their account UI) I also deprecate the respective command option with this PR.
Fixes #61