Skip to content

Releases: highsidelabs/laravel-spapi

v2.0.2

11 Sep 12:14
Compare
Choose a tag to compare

Added

  • An optional migration for dealing with the fact that Laravel's database cache fields are too small for the cache keys and values produced when we cache access tokens

v2.0.1

13 Aug 18:14
Compare
Choose a tag to compare

Fixed

  • Make cache get/set methods work properly when the cache driver doesn't support tagging
  • Re-add config/spapi.php to spapi-config publishing group

Full Changelog: v2.0.0...v2.0.1

v2.0.0

06 Aug 07:08
55316ce
Compare
Choose a tag to compare

Support for jlevers/selling-partner-api v7 and Laravel 11

If you're upgrading from v1.x, refer to the README to see how to use v2.x, because basically everything has changed. If you have a v2.x multi-seller setup, you can remove the unnecessary AWS fields from the spapi_credentials table like so:

$ php artisan vendor:publish --tag spapi-v2-upgrade
$ php artisan migrate

Full Changelog: v1.2.2...v2.0.0

v1.2.2

19 Aug 23:56
Compare
Choose a tag to compare

Added

  • Credentials::bustCache() method clears the access token from the cache
  • Add updating event observer to Credentials to automatically bust the cache when Credentials are updated

Full Changelog: v1.2.1...v1.2.2

v1.2.1

11 Aug 21:50
Compare
Choose a tag to compare

Added

  • The Credentials::handleRegion method allows users to customize how the region code is retrieved, in case they store the SP API region in a custom format (or in a separate model).

Full Changelog: v1.2.0...v1.2.1

v1.2.0

11 Aug 20:55
Compare
Choose a tag to compare

Changed

  • Removed API class auto-discovery and replaced it with an explicit list to speed up package initialization (#3)
  • Switched from singleton to bind for API classes in the service container, also to speed up package initialization (#3 fixed via #4, thanks @MannikJ!)

Fixed

  • When attempting to load uncached credentials in multi-seller mode with dynamic AWS credentials enabled, there was an error because we were trying to load (nonexistent) static AWs credentials. That bug is now resolved.

Added

  • You can now set the SP API library's debug flag and debug output location via the config/spapi.php file (thanks @MannikJ)

Full Changelog: v1.1.3...v1.2.0

v1.1.3

12 Jun 03:29
Compare
Choose a tag to compare

Fixed

  • Avoid throwing errors on install due to missing environment variables

Full Changelog: v1.1.2...v1.1.3

v1.1.2

08 Jun 21:13
Compare
Choose a tag to compare

Fixed

  • Bump minimum jlevers/selling-partner-api version to 5.9 to avoid conflicts in Guzzle versions

Full Changelog: v1.1.1...v1.1.2

v1.1.1

02 Mar 08:46
Compare
Choose a tag to compare

Changed

  • Removed check for dynamic AWS credentials columns when deciding whether or not to make it possible to publish the dynamic AWS update migration

Full Changelog: v1.1.0...v1.1.1

v1.1.0

17 Feb 03:05
Compare
Choose a tag to compare

Added

  • Support multi-seller installations with more than one set of AWS credentials by optionally adding AWS fields to the spapi_credentials table if the spapi.aws.dynamic config flag is true
  • Enable switching from static to dynamic AWS creds after creating the spapi_credentials with an additional stubbed migration, which is only published when using the add-aws publishing tag and when spapi.aws.dynamic is true

Changed

  • The valid values for the spapi.installation_type configuration value in config/spapi.php are now 'single' and 'multi' instead of 'singleuser' and 'multiuser'. This is a breaking change, but since we at Highside Labs are the only people using this library so far (as far as we can tell) we're not going to sweat doing a whole new major version for this change.

Full Changelog: v1.0.0...v1.1.0