sp_api_clients 2.0.0 → 2.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0627464f44e6cbe35d99ea9405211a6aebf7d2276eea6532f886d9c96a33d1d8
-  data.tar.gz: 6dd7221be23aada8e99d15d247d33b6c22d3e96e0b21e974253e3dd9df89e29d
+  metadata.gz: c71c8c23330671f30dac0062ae042e7bd71023191bcd63d162ebd82b8ae84dbf
+  data.tar.gz: 19f449b014108e97650d7919aa768c5a77d0e1361532ebfa256309ff1447a7bc
 SHA512:
-  metadata.gz: defb167f4de77e60be1b1c21dfeab17017717e70117a3a3f41539296cc0cdbee17c5b3d449630b4df7b9c8cfec2433f6f1624de6840fc4dcad7f32092e82197e
-  data.tar.gz: c917ac15645bed83f5e5362eec43807b23e81acd4c4555c9ef3a12c1660d48c0d161aa89511035ccb5a1dcf8a8fa8f7280731500b064c9824829178789d1a333
+  metadata.gz: 19b0f5eb3625e1150e2536598544f9a43be902a995d8fdb362003db4f553cc1b9a49f422f987035548db38a47aa7e524ea56d1340ff679c8921ef957aba48b3f
+  data.tar.gz: 12f26dd1a81dc282579b186b5c4ac554888b321fdebb2a50dd1561df04e989f1d21138eac130f2587ad47f54a6f7321403d01829415d29a20ef8b48838407bf0

data/CHANGELOG.md

@@ -6,6 +6,26 @@ Notable changes to this gem. The format follows
 Changes that only track updates to Amazon's API models are not
 considered breaking and do not trigger a major version bump.
 
+## [2.0.1] - 2026-09-07
+
+### Added
+
+- `examples/auth_check.rb`, a standalone script that shows which
+  credentials SP-API accepts. It calls the Orders API with a made-up
+  token and with a real access token, then asks LWA for a refresh with
+  and without the app credentials, and prints what each answer means.
+  It depends on nothing but this gem, or on Net::HTTP when the gem is
+  not in the bundle. `examples/` is not part of the built gem.
+- `rake release:prepare[X.Y.Z]` prepares a release on a laptop: it
+  runs the suite, sets the version, dates the CHANGELOG entry, relocks
+  the lockfiles, commits and tags. Pushing the tag still publishes.
+
+### Changed
+
+- The README and the spec comments no longer name any particular
+  consumer of the gem. `lib/` and `vendor/` are unchanged; for a
+  consumer, 2.0.1 is 2.0.0 with a new README.
+
 ## [2.0.0] - 2026-09-03
 
 ### Added

data/README.md

@@ -28,11 +28,11 @@ Because of that, each API must be required explicitly:
 ```ruby
 require 'amazon_sp_clients' # or 'sp_api_clients'; Bundler.require does this for you
 
-# in active_cart
+# a project that reads orders
 require 'amazon_sp_clients/sp_orders_v0' # Orders API
 # ...and others
 
-# in active_fulfillment
+# a project that reads inventory
 require 'amazon_sp_clients/sp_fba_inventory' # FBA Inventory API
 # ...and others
 ```
@@ -260,25 +260,26 @@ pending publisher expires when the first push does not follow soon
 (12 hours at the time of writing). After the first release the
 publisher belongs to the gem and stays.
 
-1. Set `AmazonSpClients::VERSION` in `lib/amazon_sp_clients/version.rb`.
-2. Re-lock all three lockfiles, or CI's frozen install fails:
+1. Write the CHANGELOG entry under a `## [X.Y.Z]` heading. The task
+   adds the date.
+2. Run the release task. It refuses a dirty tree, a bad version, an
+   existing tag or a missing CHANGELOG entry. Then it runs the suite,
+   sets `AmazonSpClients::VERSION`, relocks all three lockfiles (or
+   CI's frozen install fails), commits `Release X.Y.Z` and creates the
+   annotated tag `vX.Y.Z`. Nothing is pushed.
 
    ```sh
-   bundle lock --local
-   BUNDLE_GEMFILE=gemfiles/faraday_1.gemfile bundle lock --local
-   BUNDLE_GEMFILE=gemfiles/faraday_2.gemfile bundle lock --local
+   bundle exec rake 'release:prepare[X.Y.Z]'
    ```
 
-3. Give the CHANGELOG entry its release date: `## [X.Y.Z] - YYYY-MM-DD`.
-   The workflow stops when the version has no entry.
-4. Commit, then push an annotated tag on that commit:
+3. Push the branch and the tag. The task prints the exact command:
 
    ```sh
-   git tag -a vX.Y.Z -m 'vX.Y.Z'
-   git push origin vX.Y.Z
+   git push origin <branch> vX.Y.Z
    ```
 
 The tag must be `v` plus the version, or the workflow stops before it
 builds. rubygems.org rejects a version it already has, so a failed
-release needs a new version and a new tag, not a re-run. `rake release`
-is disabled; it would tag and push from a laptop.
+release needs a new version and a new tag, not a re-run. That is why
+the task runs the suite before it tags. The bundler `rake release` is
+disabled; it would push the gem from a laptop.

data/lib/amazon_sp_clients/version.rb

@@ -1,3 +1,3 @@
 module AmazonSpClients
-  VERSION = '2.0.0'.freeze
+  VERSION = '2.0.1'.freeze
 end

data/sp_api_clients.gemspec

@@ -25,7 +25,7 @@ Gem::Specification.new do |spec|
   # Only lib/, vendor/, the gemspec and the top-level docs ship. Tests,
   # the generator, CI config, dotfiles and the dev tooling stay behind.
   dev_files = %r{
-    ^(test|spec|features|amzn-models|gemfiles|bin)/ |
+    ^(test|spec|features|amzn-models|gemfiles|bin|examples|tasks)/ |
     ^lib/generator |
     ^\. |
     ^(Gemfile(\.lock)?|Rakefile|CLAUDE\.md|codegen-config\.yml|selling-partner-api-models\.sha)$

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sp_api_clients
 version: !ruby/object:Gem::Version
-  version: 2.0.0
+  version: 2.0.1
 platform: ruby
 authors:
 - Dropstream