Currently the latest release is 0.2.0, which is outdated. It still uses the old way to calculate HMACs, which (probably) leads to requests containing special characters failing.
Composer defaults to 0.2.0 for "minimum-stability": "stable" and "prefer-stable": true, which means most people using the package will run into this issue.
On a quick scan, none of the commits seem to be a breaking change, so I would like to propose promoting to 0.3.0 or 0.2.1, depending on if there is any new features in this release.
Meanwhile, users can either roll their own SDK or change the version constraint to dev-master in their composer.json to be able to make use of HMAC v2:
Currently the latest release is
0.2.0, which is outdated. It still uses the old way to calculate HMACs, which (probably) leads to requests containing special characters failing.Composer defaults to
0.2.0for "minimum-stability": "stable" and "prefer-stable": true, which means most people using the package will run into this issue.On a quick scan, none of the commits seem to be a breaking change, so I would like to propose promoting to
0.3.0or0.2.1, depending on if there is any new features in this release.Meanwhile, users can either roll their own SDK or change the version constraint to
dev-masterin theircomposer.jsonto be able to make use of HMAC v2: