fix: build workspace packages before migration tests
This commit is contained in:
@@ -25,11 +25,13 @@ Docker and the Docker Compose plugin are required for the live suite:
|
||||
pnpm test:migrations:integration
|
||||
```
|
||||
|
||||
The command starts the repository's pinned PostgreSQL image in a unique Compose project, waits for
|
||||
bounded health readiness, runs the production PostgreSQL adapter and migration services, and then
|
||||
removes the container, network, and volume. Each scenario also receives a safely named disposable
|
||||
database. Direct host runs use a Docker-assigned random port bound only to `127.0.0.1`; a
|
||||
containerized Gitea job joins the isolated Compose network and uses the PostgreSQL service name.
|
||||
The command first builds the workspace through the repository's Turbo build graph, then starts the
|
||||
repository's pinned PostgreSQL image in a unique Compose project, waits for bounded health
|
||||
readiness, runs the production PostgreSQL adapter and migration services, and removes the
|
||||
container, network, and volume. A build failure occurs before Docker provisioning. Each scenario
|
||||
also receives a safely named disposable database. Direct host runs use a Docker-assigned random
|
||||
port bound only to `127.0.0.1`; a containerized Gitea job joins the isolated Compose network and
|
||||
uses the PostgreSQL service name.
|
||||
|
||||
The live suite proves fresh read-only planning, initial and incremental application, genuine
|
||||
no-op behavior, exact applied checksums and history, edited or corrupt history rejection,
|
||||
|
||||
Reference in New Issue
Block a user