Update hivegrid-cloud reference to latest main
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
e98d38e716
commit
7b21524c86
3781 files changed
+373484
-225607
No files matched your search
@@ -2,7 +2,7 @@
|
||||
|
||||
## Purpose
|
||||
|
||||
The database CI gate verifies that the repository can reach its configured database and that Prisma reports migration status through the package-owned database boundary. The root command `pnpm run verify:db-migrate-status` shells through `pnpm --filter @toolctrl/db prisma:migrate:status`, so CI and local checks use the same `@toolctrl/db` command surface instead of invoking Prisma directly.
|
||||
The database CI gate verifies that the repository can reach its configured database and that Prisma reports migration status through the package-owned database boundary. The root command `pnpm run verify:db-migrate-status` shells through `pnpm --filter @hivegrid/db prisma:migrate:status`, so CI and local checks use the same `@hivegrid/db` command surface instead of invoking Prisma directly.
|
||||
|
||||
This is a non-E2E gate. Auto-Mode does not run browser, Playwright, Cypress, or other E2E checks for this task, and the database job must not include browser automation commands.
|
||||
|
||||
@@ -29,7 +29,7 @@ The verifier fails before spawning Prisma when `DATABASE_URL` is absent. It does
|
||||
|
||||
## CI job order
|
||||
|
||||
The Gitea workflow includes a `database` job that depends on `quality`. The job installs dependencies with the pinned pnpm setup, generates the database client through `@toolctrl/db`, and then runs the non-E2E status verifier.
|
||||
The Gitea workflow includes a `database` job that depends on `quality`. The job installs dependencies with the pinned pnpm setup, generates the database client through `@hivegrid/db`, and then runs the non-E2E status verifier.
|
||||
|
||||
The database job runs migration status only. It must not run `migrate deploy`, seed commands, browser automation, or E2E checks.
|
||||
|
||||
@@ -43,14 +43,14 @@ The database job runs migration status only. It must not run `migrate deploy`, s
|
||||
- status outcome: success or failure classification
|
||||
- sanitized stdout/stderr excerpt: a bounded output excerpt with secrets redacted
|
||||
|
||||
A success means Prisma migration status completed through the `@toolctrl/db` boundary. It does not apply migrations, seed data, or prove browser-facing behavior.
|
||||
A success means Prisma migration status completed through the `@hivegrid/db` boundary. It does not apply migrations, seed data, or prove browser-facing behavior.
|
||||
|
||||
## Failure diagnostics
|
||||
|
||||
Common failures and first checks:
|
||||
|
||||
- Missing `DATABASE_URL`: confirm the CI secret exists and is scoped to the migrate-status step.
|
||||
- Spawn failure: confirm pnpm dependencies are installed and the `@toolctrl/db` package scripts are available.
|
||||
- Spawn failure: confirm pnpm dependencies are installed and the `@hivegrid/db` package scripts are available.
|
||||
- Non-zero Prisma exit: inspect the sanitized stdout/stderr excerpt and the Prisma status message in CI logs.
|
||||
- Workflow contract failure: run `pnpm run verify:gitea-ci-workflow` and fix the database job shape before changing the database verifier.
|
||||
|
||||
|
||||
Reference in new issue
Block a user