@byollm/relay 0.1.0-alpha.38 → 0.1.0-alpha.39

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.
Files changed (2) hide show
  1. package/README.md +4 -4
  2. package/package.json +5 -5
package/README.md CHANGED
@@ -1,5 +1,5 @@
1
1
  > [!WARNING]
2
- > **Alpha (`0.1.0-alpha.38`) — under active development. Don't use this yet.**
2
+ > **Alpha (`0.1.0-alpha.39`) — under active development. Don't use this yet.**
3
3
  >
4
4
  > This is a walking skeleton. It routes real jobs between real daemons and real
5
5
  > sites, and it is the fixture byollm_009 freezes against — but it keeps its
@@ -72,7 +72,7 @@
72
72
  > packages published and `@byollm/server` did not: a Sigstore
73
73
  > transparency-log 409 on its provenance attestation. The workflow's
74
74
  > "already published" guard correctly refuses to resume a partial publish,
75
- > so `0.1.0-alpha.38` is that release, whole.
75
+ > so `0.1.0-alpha.39` is that release, whole.
76
76
  >
77
77
  > If you run the Supabase adapter, `alpha.21` needs
78
78
  > `20260819010000_completed_by_lease_id.sql`: alpha.19 shipped §3.6's
@@ -153,7 +153,7 @@ daemons pin at pairing, verified against the `sites` half of the projection.
153
153
  Nothing here trusts a `siteId` in a body or a query string.
154
154
 
155
155
  That is newer than the rest of this package. The site plane took the caller's
156
- word for who it was until `0.1.0-alpha.38`, which on a relay reachable from the
156
+ word for who it was until `0.1.0-alpha.39`, which on a relay reachable from the
157
157
  internet is an open enqueue endpoint into consenting users' machines and an
158
158
  open read of who is online. It was blind the whole time — nothing could open a
159
159
  payload — and blind is not the same as safe.
@@ -161,7 +161,7 @@ payload — and blind is not the same as safe.
161
161
  If you are running this: the site plane is authenticated but this is still a
162
162
  single-tenant relay with in-memory state. One site, one replica.
163
163
 
164
- ## Breaking in `0.1.0-alpha.38`: `RelayState` is async
164
+ ## Breaking in `0.1.0-alpha.39`: `RelayState` is async
165
165
 
166
166
  Every method on `RelayState` now returns a `Promise`, and `Relay.sweep()` and
167
167
  `debugPage()` with it. `RelayState.requeue` is private — it was only ever a
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@byollm/relay",
3
- "version": "0.1.0-alpha.38",
3
+ "version": "0.1.0-alpha.39",
4
4
  "type": "module",
5
5
  "description": "The reference relay: routes sealed byollm jobs between sites and daemons, holding no decryption keys by construction.",
6
6
  "license": "MIT",
@@ -31,7 +31,7 @@
31
31
  ],
32
32
  "dependencies": {
33
33
  "zod": "^4.1.13",
34
- "@byollm/protocol": "0.1.0-alpha.38"
34
+ "@byollm/protocol": "0.1.0-alpha.39"
35
35
  },
36
36
  "publishConfig": {
37
37
  "access": "public"
@@ -39,9 +39,9 @@
39
39
  "devDependencies": {
40
40
  "@supabase/supabase-js": "^2.112.2",
41
41
  "vitest": "^4.1.10",
42
- "@byollm/conformance": "0.1.0-alpha.38",
43
- "byollm": "0.1.0-alpha.38",
44
- "@byollm/server": "0.1.0-alpha.38"
42
+ "byollm": "0.1.0-alpha.39",
43
+ "@byollm/conformance": "0.1.0-alpha.39",
44
+ "@byollm/server": "0.1.0-alpha.39"
45
45
  },
46
46
  "peerDependencies": {
47
47
  "vitest": ">=3"