CI: npm run check fails on drizzle-orm schema overload errors after self-contained workflow rewrite #9

New issue

Closed

opened 2026-09-16 19:15:05 +00:00 by Mark · 1 comment

Mark commented

2026-09-16 19:15:05 +00:00

Owner

"## Context\n\nThe AuWoMe/Drift CI workflow was rewritten (commit 710627d fix(ci): self-contained workflow — drop unreachable JS actions) to remove unreachable actions/checkout@v4 / actions/setup-node@v4 uses: lines and run in docker.io/library/node:20-bookworm instead. Verified as wired correctly: post-rewrite runs are no longer cancelled at 'Set up job' and reach the npm ci step.\n\nA follow-up commit 71c93905 fix(#8): pin eslint-plugin-react-refresh to ^0.4.20 for eslint 8 compatibility resolved the npm ci ERESOLVE (peer-dep conflict), so the post-rewrite recipe's first two steps (npm ci, npm run build) now succeed. The third step (npm run check) still fails.\n\n## Reproduction\n\npush to main (commit 71c93905) → run 7032 (status=failure, duration=127s)\nhtml_url: https://forgejo.tail018ac4.ts.net/AuWoMe/Drift/actions/runs/19\n\nPer the commit message of 71c93905:\n\n> Verified:\n> - npm ci exits 0 (no ERESOLVE)\n> - npm run build succeeds\n> - npm run check still fails (drizzle-orm schema overload errors) — separate bug\n\n## Acceptance criteria for closing this issue\n\n- npm run check exits 0 in the docker.io/library/node:20-bookworm container.\n- A fresh push to main produces a Forgejo Actions run ending in success (or completed with all steps green).\n\n## References\n\n- Verification card: kanban t_8b7daaab (tasker-worker, completed 2026-09-16)\n- Rewrite card: t_b55e19fa (done) — workflow recipe is correct; this issue is the app-level debt.\n- Run 7032 evidence: forgejo-api.sh GET /repos/AuWoMe/Drift/actions/runs/7032 → {status: failure, duration: 127, commit_sha: 71c93905...}\n- Note: the Forgejo jobs API endpoint GET /api/v1/repos/AuWoMe/Drift/actions/runs//jobs returns 404 on this Forgejo 13.0.4 instance for every run, including pre-existing ones — this is a separate platform capability gap (forgejo#11792 / gitea#35382), not an AuWoMe/Drift bug."

"## Context\n\nThe AuWoMe/Drift CI workflow was rewritten (commit 710627d fix(ci): self-contained workflow — drop unreachable JS actions) to remove unreachable actions/checkout@v4 / actions/setup-node@v4 uses: lines and run in docker.io/library/node:20-bookworm instead. Verified as wired correctly: post-rewrite runs are no longer cancelled at 'Set up job' and reach the npm ci step.\n\nA follow-up commit 71c93905 fix(#8): pin eslint-plugin-react-refresh to ^0.4.20 for eslint 8 compatibility resolved the npm ci ERESOLVE (peer-dep conflict), so the post-rewrite recipe's first two steps (npm ci, npm run build) now succeed. The third step (npm run check) still fails.\n\n## Reproduction\n\npush to main (commit 71c93905) → run 7032 (status=failure, duration=127s)\nhtml_url: https://forgejo.tail018ac4.ts.net/AuWoMe/Drift/actions/runs/19\n\nPer the commit message of 71c93905:\n\n> Verified:\n> - npm ci exits 0 (no ERESOLVE)\n> - npm run build succeeds\n> - npm run check still fails (drizzle-orm schema overload errors) — separate bug\n\n## Acceptance criteria for closing this issue\n\n- npm run check exits 0 in the docker.io/library/node:20-bookworm container.\n- A fresh push to main produces a Forgejo Actions run ending in success (or completed with all steps green).\n\n## References\n\n- Verification card: kanban t_8b7daaab (tasker-worker, completed 2026-09-16)\n- Rewrite card: t_b55e19fa (done) — workflow recipe is correct; this issue is the app-level debt.\n- Run 7032 evidence: forgejo-api.sh GET /repos/AuWoMe/Drift/actions/runs/7032 → {status: failure, duration: 127, commit_sha: 71c93905...}\n- Note: the Forgejo jobs API endpoint GET /api/v1/repos/AuWoMe/Drift/actions/runs/<id>/jobs returns 404 on this Forgejo 13.0.4 instance for every run, including pre-existing ones — this is a separate platform capability gap (forgejo#11792 / gitea#35382), not an AuWoMe/Drift bug."

Mark added the

bug

triage-approved

labels

2026-09-16 19:15:05 +00:00

Mark referenced this issue from a commit

2026-09-16 19:22:38 +00:00

fix(#9): drop pgTable variants, switch storage layer to sqlite-only

Mark referenced this issue from a pull request that will close it,

2026-09-16 19:22:52 +00:00

fix(#9): drop pgTable variants, switch storage layer to sqlite-only #11

Mark closed this issue

2026-09-16 19:23:04 +00:00

Mark reopened this issue

2026-09-17 18:02:54 +00:00

Mark referenced this issue from a commit

2026-09-17 18:13:20 +00:00

fix(#9): clear drizzle-orm schema overload errors blocking npm run check

Mark referenced this issue

2026-09-17 18:17:36 +00:00

CI workflow: all runs failing or cancelling since repo creation #7

Mark added the

in-progress

label

2026-09-18 00:57:54 +00:00

Mark commented

2026-09-18 01:04:22 +00:00

Author

Owner

Fixed in commit 8bfee31fcc (fix(#9): clear drizzle-orm schema overload errors blocking npm run check). Dropped seven dead *Sqlite drizzle tables in shared/schema.ts that were never imported anywhere — runtime SQLite was already using raw CREATE TABLE via createSqliteTables, so the dead schemas were the only thing tripping the tsc overload errors.

Verified on Forgejo Actions run 7043 (commit 8bfee31, push to main):

status: success
duration: 129s
all steps green (npm ci, npm run build, npm run check)

Closing.

Fixed in commit 8bfee31fcc596d4da183d22f96c4185b4509f32f (`fix(#9): clear drizzle-orm schema overload errors blocking npm run check`). Dropped seven dead `*Sqlite` drizzle tables in shared/schema.ts that were never imported anywhere — runtime SQLite was already using raw CREATE TABLE via `createSqliteTables`, so the dead schemas were the only thing tripping the tsc overload errors. Verified on Forgejo Actions run 7043 (commit 8bfee31, push to main): - status: success - duration: 129s - all steps green (npm ci, npm run build, npm run check) Closing.

Mark

2026-09-18 01:04:37 +00:00