Skip to content

Commit cdaf264

Browse files
authored
docs(devlog): record the v2.37.0 release and the live #3022 verification (#3043)
The 5.6 fix is published and proven on the installed runtime rather than only in CI. npm latest is 2.37.0 with gitHead 54e2274, and the tag, GitHub release and main all point at that same commit. Both required gates passed on that exact SHA as push events. Two things in the release path are worth writing down because both would have let a "released" claim stand on nothing. bun add -g reused a cached 2.37.0 built the previous day, before the fix existed. The version string matched and the bytes did not, so the only check that settles it is grepping the installed file. --force fixed it. The running proxy was serving the primary checkout, which sat four commits behind dev while /healthz reported version 2.37.0. So the health endpoint agreed with the release and the code did not. Fast-forwarded and restarted onto the global install. On that runtime, ocx models live lists sol, terra and luna as native/enabled, and /v1/models, /api/models and ocx export all carry them. That also confirms the warm path for the three surfaces #3023 names, which scopes the remaining wp6 work to TTL expiry rather than to the rows themselves.
1 parent 4180067 commit cdaf264

1 file changed

Lines changed: 35 additions & 0 deletions

File tree

‎devlog/_plan/260831_prio70_entitlement_and_spill_train/070_outcome.md‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -107,3 +107,38 @@ genuine stable-fixed-point loop, `B=5000`/`R=4000` with the fallback receiving i
107107
reserved slice, and the shared ACL deadline reaching both hardeners. The review found
108108
one high defect: supersession reaches the state tracking but not the writer, so an
109109
abandoned writer can still publish to the filesystem and orphan a temp. Sent back.
110+
111+
## v2.37.0 released — #3022 verified live
112+
113+
The 5.6 fix is published and proven on the installed runtime, not just in CI.
114+
115+
- npm `@bitkyc08/[email protected]` on `latest`; `gitHead` = `54e2274cff231631c0ea2ff12574ff03829d5fe6`
116+
- tag `v2.37.0` and the GitHub release both point at that same commit
117+
- `main` = `54e2274cf` (promotion PR #3037), `dev` = `4180067b4` and an ancestor of it
118+
119+
Both required gates passed on the exact release SHA as push events: Cross-platform CI
120+
and Service lifecycle. `enforce-target` fails on any promotion by construction —
121+
`ALLOWED_BASES` is `["dev"]` — which is why #3002 (v2.36.0) merged in the same state.
122+
123+
Release-path proof, in order:
124+
125+
1. The published tarball carries both changes:
126+
`MEASURED_GATED_CLIENT_VERSION_MINIMUM = "0.144.0"` at `:88` and
127+
`const usable = models !== null && models.size > 0` at `:472`.
128+
2. The global install had to be forced. `bun add -g` reused a cached 2.37.0 from
129+
Aug 30 that predated the fix — same version string, old bytes. Worth remembering:
130+
a version match is not a content match, and `grep` on the installed file is the
131+
check that actually settles it.
132+
3. The running proxy was serving the primary checkout, which sat 4 commits behind
133+
`dev` while reporting `version: 2.37.0`. So `/healthz` agreed with the release
134+
and the code did not. Fast-forwarded the checkout and restarted onto the global
135+
install (PID 57341, `~/.bun/install/global/.../@bitkyc08/opencodex`).
136+
4. On that runtime: `ocx models live --provider openai` lists `gpt-5.6-sol`,
137+
`-terra` and `-luna` as native/enabled; `/v1/models` returns all three;
138+
`/api/models` and `ocx export --client opencode --json` carry them too.
139+
140+
That last point matters beyond #3022: the three surfaces #3023 names were checked on
141+
a warm roster and all carry the gated rows. #3023 is about what happens once
142+
`MODEL_ROSTER_TTL_MS` expires, so this is not a NOOP for it — but it does confirm
143+
the warm path is intact and the wp6 work is scoped to expiry, not to the rows
144+
themselves.

0 commit comments

Comments
 (0)