@recapi/client 0.1.2 → 0.2.0

package/README.md

@@ -16,7 +16,7 @@ are, gzipped, and browsers cache them for a year:
 
 ```html
 <script type="module">
-  import { createClient } from 'https://api.example.com/sdk/0.1.2/index.js';
+  import { createClient } from 'https://api.example.com/sdk/0.2.0/index.js';
 
   const recapi = createClient({ apiKey: 'rk_pub_…', baseUrl: 'https://api.example.com' });
   recapi.track('item-42', 'view');    // and the calls of the quick start below
@@ -508,6 +508,8 @@ minifier, to keep zero dev dependencies.
 
 ## Changes
 
+- 2026-10-30: version 0.2.0, the same code as 0.1.2: the first version
+  published to npm by GitHub Actions (trusted publishing), with provenance.
 - 2026-10-26: version 0.1.2. When `GET /v1/popular` fails too (recapi is
   down altogether), `recommend()` resolves with an empty list
   (`fallback: true`) instead of rejecting, and reports both errors to
@@ -540,8 +542,8 @@ to `published.json` (the digest is `sha256sum src/*.js | sha256sum`, then
 each file's exports), and change the `/sdk/<version>/` paths in this
 README and `docs/api.md` (the quick start follows by itself). Never edit
 an existing entry of `published.json`.
-Once production runs that version, the release service publishes it to
-npm as `@recapi/client` ([deployment.md](../../docs/deployment.md#publishing-the-javascript-library)):
+Once production runs that version, the release service has GitHub publish
+it to npm as `@recapi/client` ([deployment.md](../../docs/deployment.md#publishing-the-javascript-library)):
 nobody runs `npm publish` by hand.
 
 Every older path, whatever its version number, redirects to the new

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@recapi/client",
-  "version": "0.1.2",
+  "version": "0.2.0",
   "description": "Browser and Node client for the recapi recommendation API: local decayed history, event batching, attribution.",
   "type": "module",
   "main": "./src/index.js",