ifr-sdk 0.4.0 → 0.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +20 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -5,11 +5,18 @@ sessions. The package currently supports Ethereum Mainnet only.
|
|
|
5
5
|
|
|
6
6
|
## Availability
|
|
7
7
|
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
8
|
+
`ifr-sdk` 0.4.0 was published to npm on 9 October 2026 as the explicitly approved, one-time
|
|
9
|
+
manual bootstrap without provenance. This repository prepares the docs-only 0.4.1 patch; it is
|
|
10
|
+
not published until the separate release gate succeeds. Every subsequent version uses
|
|
11
|
+
`.github/workflows/sdk-publish.yml`, dispatched manually on protected `main`, which checks the
|
|
12
|
+
release gate, waits for owner approval, tests the package and publishes with npm provenance through
|
|
13
|
+
Trusted Publishing. To install the verified bootstrap version:
|
|
14
|
+
|
|
15
|
+
```bash
|
|
16
|
+
npm install --save-exact ifr-sdk@0.4.0
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
Alternatively, build and pack a reviewed versioned artifact from the repository:
|
|
13
20
|
|
|
14
21
|
```bash
|
|
15
22
|
cd apps/sdk
|
|
@@ -89,7 +96,7 @@ challenge message before any signature is requested.
|
|
|
89
96
|
|
|
90
97
|
### Compatibility: wallet-free seller challenge (0.4.0)
|
|
91
98
|
|
|
92
|
-
The Benefits backend no longer echoes `walletAddress` in `GET /api/seller/auth-message` (owner
|
|
99
|
+
The owner-B Benefits backend no longer echoes `walletAddress` in `GET /api/seller/auth-message` (owner
|
|
93
100
|
decision B: no wallet in the challenge URL, response or storage; a legacy `walletAddress` query
|
|
94
101
|
parameter is ignored). Earlier `ifr-sdk` builds up to 0.3.0 (never published to npm; only repository
|
|
95
102
|
tarballs) require `challenge.walletAddress` in that response and reject every challenge from the new backend ("mismatched seller authorization
|
|
@@ -98,6 +105,13 @@ challenge"), so `createCheckout()` and `redeemCheckout()` break. Release order:
|
|
|
98
105
|
wallet-free challenge, and tell integrators to upgrade first. Publishing is a separate release gate. The caller supplies a wallet-native `signMessage`
|
|
99
106
|
callback; the SDK never accepts or stores private keys, seed phrases or persistent seller secrets.
|
|
100
107
|
|
|
108
|
+
**Deployment boundary (9 October 2026):** the public production Benefits backend has not yet
|
|
109
|
+
activated the owner-B migration. SDK 0.4.x `createCheckout()` and `redeemCheckout()` require the
|
|
110
|
+
wallet-free owner-B challenge API and are not compatible with the older wallet-bound API. Package
|
|
111
|
+
publication does not migrate a database or enable partner rewards. POS integrators must coordinate
|
|
112
|
+
their checkout upgrade with the separately approved backend rollout; read-only IFR methods do not
|
|
113
|
+
depend on that rollout. Version 0.4.1 changes documentation/version metadata only, not runtime code.
|
|
114
|
+
|
|
101
115
|
## Verification
|
|
102
116
|
|
|
103
117
|
```bash
|