openreceive-server 0.2.1 → 0.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 815016906827bfc710461c1d68490612651e561647e844490366a835efd4ec5b
-  data.tar.gz: 35be8788e0f8bbcc83b2fdf6771e0bbce272267ef6c76151b739e23639ff56fe
+  metadata.gz: 6787423e982a56751f291210d207d6ff4c0ccd49eb438f087cc749e35b9eaae6
+  data.tar.gz: 73d06359d629e52245de41c2e6fca1068765572325bc9250acd61499904c13e1
 SHA512:
-  metadata.gz: 96c1bbbea13c33b366f6f09a30104fa3340b49500ee6ecfd97475155c0b280981a534ba20df800b362d193cdc6cd11c4bbe6c16a6c8bd20e9e8083b6f0a5d9af
-  data.tar.gz: cfb1f18622c9e424e0f10754da453c7be4300137a204f8e6742cdd38f37587b37afa782a4b6bbc4bf6e55cc5e51727f2d6d9f459806fb4a5db5a8741efd00bdd
+  metadata.gz: aa11b53030d9c8c91ab02f39ebd25c57709c540ce351b2a09dc864260d7868bda54f38f99229c374d910e6624eb4d53fb007bdfc91bd364427b15c51513c3dfd
+  data.tar.gz: c88b8c1e9576e841b8be7013e78592c25821a76ae97a2fc145f7b8adc555571b1e1b63b5f1d8b3c8d8cfad7869d44a75faf2720834c74a3badbcc3406d85db33

data/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## 0.2.3 - 2026-08-25
+
+The Ruby gems release in lockstep with the npm workspace version. The full
+release narrative lives in the repository-root
+[CHANGELOG](https://github.com/openreceive/openreceive/blob/master/CHANGELOG.md);
+entries here are scoped to this gem.
+
+- **`POST /checkouts` now echoes `payment_methods`** (HTTP contract 0.4.1),
+  amount-aware against the minted attempt's own invoice amount and served on
+  the re-fetch path too. `prepare` and `payments/check` already did; the mint
+  alone did not, so any client without a library-side merge lost its pay-in
+  catalog the moment it minted Lightning.
+
+## 0.2.2 - 2026-08-25
+
+The Ruby gems release in lockstep with the npm workspace version. The full
+release narrative lives in the repository-root
+[CHANGELOG](https://github.com/openreceive/openreceive/blob/master/CHANGELOG.md);
+entries here are scoped to this gem.
+
+- No functional change. `nwc-ruby` is still deliberately NOT a dependency of
+  this gem: a Rack host injects its own NWC client and this gem never reaches
+  for one. The Rails engine — the exception that rationale already named — now
+  declares it, and the comment here says so.
+
 ## 0.2.1 - 2026-08-24
 
 The Ruby gems release in lockstep with the npm workspace version. The full

data/lib/openreceive/server/request_handler.rb

@@ -73,7 +73,14 @@ module OpenReceive
                        )
                      end
           commit(checkout, nil, request) unless resolved["payment_hash"]
-          success(201, { "checkout" => checkout }, request_id)
+          # The catalog rides along with the mint for the same reason it rides
+          # along with prepare and payments/check (mirrors the JS handler): a
+          # client that just minted Lightning must not lose the pay-in options
+          # it renders its picker from. Amount-aware, against this attempt's
+          # committed invoice amount — and served on the re-fetch path too, so
+          # a repeated create answers with the same shape it first did.
+          payment_methods = @service.list_swap_options(amount_msats: checkout["amount_msats"])
+          success(201, { "checkout" => checkout, "payment_methods" => payment_methods }, request_id)
         end
       end
 

data/lib/openreceive/server/version.rb

@@ -2,6 +2,6 @@
 
 module OpenReceive
   module Server
-    VERSION = "0.2.1"
+    VERSION = "0.2.3"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: openreceive-server
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.2.3
 platform: ruby
 authors:
 - OpenReceive
@@ -15,14 +15,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.2.1
+        version: 0.2.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.2.1
+        version: 0.2.3
 description: 'Server building blocks for OpenReceive: a storage-free Service that
   mirrors the Node engine and a framework-agnostic Rack app implementing the shipped
   HTTP routes while the host owns order and payment persistence. Receive-only: it