@urun-sh/core 0.2.0 → 0.2.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/CHANGELOG.md +4 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.2.1
|
|
4
|
+
|
|
5
|
+
- Republish of the 0.2.0 line. `npm publish` reported success for `@urun-sh/core@0.2.0` / `@urun-sh/react@0.2.0` but the version never landed in the public npm packument (a registry-side persistence failure — npm/npm#20851), leaving 0.2.0 unresolvable via `npm install` and occupied (so not re-publishable). Bumped to 0.2.1 to ship a clean, resolvable release. No source changes vs 0.2.0.
|
|
6
|
+
|
|
3
7
|
## 0.1.49
|
|
4
8
|
|
|
5
9
|
- Recordings lifecycle & retention client (L3). New `RecordingsClient` / `createRecordingsClient` wired to the org-scoped recordings edge function (`/functions/v1/recordings`): `list(sessionId?)`, `get`, `retain(id, duration)`, `pin`, `unpin`, `permanent`, `delete`. Bearer auth resolves `getAccessToken ?? jwt ?? apiKey` and does one force-refresh retry on 401 (mirrors the gateway pattern). The org is derived server-side — `org_id` is never sent.
|