@powerhousedao/switchboard 6.2.2-dev.72 → 6.2.2-dev.74

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/Auth.md CHANGED
@@ -173,6 +173,32 @@ export AUTH_ENABLED=true
173
173
  export ADMINS="0x111,0x222,0x333"
174
174
  ```
175
175
 
176
+ `AUTH_ENABLED` does two things: it selects the authorization policy
177
+ (`ADMIN_ONLY` instead of `OPEN`) **and** it makes the middleware verify the
178
+ bearer so `ctx.user` is populated. `RESOLVE_CALLER_IDENTITY` separates the
179
+ second from the first:
180
+
181
+ ```bash
182
+ # Read the bearer and populate ctx.user, whatever the policy is
183
+ export RESOLVE_CALLER_IDENTITY=true
184
+ ```
185
+
186
+ | | `AUTH_ENABLED` unset | `AUTH_ENABLED=true` |
187
+ | -------------------------------- | -------------------------- | ------------------------------- |
188
+ | `RESOLVE_CALLER_IDENTITY` unset | no user, `OPEN` | user resolved, `ADMIN_ONLY` |
189
+ | `RESOLVE_CALLER_IDENTITY=true` | **user resolved, `OPEN`** | user resolved, `ADMIN_ONLY` |
190
+
191
+ It defaults to whatever `AUTH_ENABLED` is, so a deployment that never sets it
192
+ behaves exactly as before. The bold cell is the combination `AUTH_ENABLED`
193
+ alone cannot express, and the one a custom subgraph needs when it does its own
194
+ authorization: its resolvers learn who is calling without every non-admin
195
+ being locked out of switchboard.
196
+
197
+ It **resolves** an identity and enforces nothing — a request with no token is
198
+ still admitted, with no user. Verification is otherwise identical to
199
+ `AUTH_ENABLED=true`, Renown credential check included, so an invalid token is
200
+ still a 401.
201
+
176
202
  #### Configuration File Method
177
203
 
178
204
  ```json
package/CHANGELOG.md CHANGED
@@ -1,3 +1,26 @@
1
+ ## 6.2.2-dev.74 (2026-09-02)
2
+
3
+ This was a version bump only for @powerhousedao/switchboard to align it with other projects, there were no code changes.
4
+
5
+ ## 6.2.2-dev.73 (2026-09-02)
6
+
7
+ ### 🚀 Features
8
+
9
+ - **reactor-api:** resolve the caller's identity without enforcing a policy ([#2953](https://github.com/powerhouse-inc/powerhouse/pull/2953))
10
+ - **reactor:** one script runs the benchmarks and records them ([89f958f97](https://github.com/powerhouse-inc/powerhouse/commit/89f958f97))
11
+ - three bench agents and the loop that runs them back to back ([af0e7467f](https://github.com/powerhouse-inc/powerhouse/commit/af0e7467f))
12
+ - **reactor:** add zod schemas for benchmark and task records ([9869572ba](https://github.com/powerhouse-inc/powerhouse/commit/9869572ba))
13
+
14
+ ### 🩹 Fixes
15
+
16
+ - **ci:** emit an empty changed-files list without a trailing space ([366ad4d96](https://github.com/powerhouse-inc/powerhouse/commit/366ad4d96))
17
+
18
+ ### ❤️ Thank You
19
+
20
+ - Benjamin Jordan
21
+ - Claude Opus 5
22
+ - Guillermo Puente Sandoval @gpuente
23
+
1
24
  ## 6.2.2-dev.72 (2026-09-02)
2
25
 
3
26
  This was a version bump only for @powerhousedao/switchboard to align it with other projects, there were no code changes.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@powerhousedao/switchboard",
3
3
  "type": "module",
4
- "version": "6.2.2-dev.72",
4
+ "version": "6.2.2-dev.74",
5
5
  "main": "dist/index.mjs",
6
6
  "exports": {
7
7
  ".": {
@@ -41,7 +41,7 @@
41
41
  "@openfeature/core": "1.9.1",
42
42
  "@openfeature/env-var-provider": "0.3.1",
43
43
  "@openfeature/server-sdk": "1.19.0",
44
- "@powerhousedao/config": "6.2.2-dev.72",
44
+ "@powerhousedao/config": "6.2.2-dev.74",
45
45
  "@opentelemetry/api": "^1.9.0",
46
46
  "@opentelemetry/exporter-metrics-otlp-http": "^0.218.0",
47
47
  "@opentelemetry/exporter-trace-otlp-http": "^0.218.0",
@@ -55,20 +55,20 @@
55
55
  "@opentelemetry/sdk-node": "^0.218.0",
56
56
  "@opentelemetry/sdk-trace-base": "^2.7.1",
57
57
  "@opentelemetry/semantic-conventions": "^1.41.1",
58
- "@powerhousedao/opentelemetry-instrumentation-reactor": "6.2.2-dev.72",
59
- "@powerhousedao/reactor": "6.2.2-dev.72",
60
- "@powerhousedao/shared": "6.2.2-dev.72",
61
- "@powerhousedao/vetra": "6.2.2-dev.72",
62
- "@powerhousedao/reactor-api": "6.2.2-dev.72",
63
- "@powerhousedao/reactor-attachments": "6.2.2-dev.72",
64
- "@powerhousedao/reactor-drive": "6.2.2-dev.72",
65
- "@powerhousedao/reactor-group": "6.2.2-dev.72",
66
- "@powerhousedao/pglite-fs": "6.2.2-dev.72",
58
+ "@powerhousedao/opentelemetry-instrumentation-reactor": "6.2.2-dev.74",
59
+ "@powerhousedao/reactor": "6.2.2-dev.74",
60
+ "@powerhousedao/shared": "6.2.2-dev.74",
61
+ "@powerhousedao/vetra": "6.2.2-dev.74",
62
+ "@powerhousedao/reactor-api": "6.2.2-dev.74",
63
+ "@powerhousedao/reactor-attachments": "6.2.2-dev.74",
64
+ "@powerhousedao/reactor-drive": "6.2.2-dev.74",
65
+ "@powerhousedao/reactor-group": "6.2.2-dev.74",
66
+ "@powerhousedao/pglite-fs": "6.2.2-dev.74",
67
67
  "@pyroscope/nodejs": "^0.4.5",
68
- "@renown/sdk": "6.2.2-dev.72",
68
+ "@renown/sdk": "6.2.2-dev.74",
69
69
  "@sentry/node": "^10.53.1",
70
70
  "@sentry/opentelemetry": "^10.53.1",
71
- "document-model": "6.2.2-dev.72",
71
+ "document-model": "6.2.2-dev.74",
72
72
  "dotenv": "^16.4.7",
73
73
  "express": "^4.21.2",
74
74
  "kysely": "0.28.16",