Repository navigation
Requires the migration and the core everybody actually runs.
This module pinned migration v0.1.24 while the published package was v0.2.0, and api v0.6.0 against v0.6.3.
MVS lifts both in a real application, so no consumer noticed. The cost is ours: GOWORK=off go test ./... is the pass this repo treats as the real signal, precisely because a workspace masks a wrong requirement — and it was validating this module against a migration a minor behind and a core three patches behind.
migration v0.2.0 is breaking in principle, so the bump was checked rather than assumed. Two kinds of generated identifier gain the table name they lacked: a multi-column Index and a single-column UniqueKey. The DSL's output was executed under both versions and diffed, on both dialects — on Postgres only the multi-column index name moves, because UniqueKey renders as an anonymous UNIQUE (col) there and the server names the constraint itself; on MySQL both move. Nothing in this module builds schema with the DSL, so nothing here changes.
api v0.6.1 serves /build/ as well as /public/build/, v0.6.2 adds LOG_QUIET so a worker or a scheduler can ask for its own voice back, and v0.6.3 is this same migration pin one level down.