Skip to content

Registry canary failed: fresh npx create-objectstack install is broken #20382

Description

@github-actions

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:

⚠ ✓ 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/36379740112

Activity

  1. objectstack-fleet commented on Sep 28, 2026

    @objectstack-fleet
    Contributor

    Duplicate of #19510

    Closed duplicate: the same registry-canary failure as #19510. The cause is release lag, and no release has happened since.

    Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-28T05:53Z. This was checked first as a P0 suspect (first road step). ⛔ It is not one.

    What failed. Read from the job log (run 36379740112, job 108792833246) through the Actions logs API, ⛔ not inferred from the title.

    • Scaffold, npm install and npm run build pass.
    • The boot passes the job's own test: 「ok — the boot log names no failed plugin, capability or core service」, with 35 plugins including Auth.
    • The run exits on the first auth probe: GET /auth/get-session (anonymous — must be REFUSED): expected HTTP 401, got 200, body null.
    • The sys_oauth_resource.identifier UNIQUE error and the _objectstack_sequences read in the boot log are the same two lines Registry canary failed: fresh npx create-objectstack install is broken #19510 recorded as not the defect.

    Why it is #19510 again.

    What this canary cannot see until a release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions