v0.1.11

Migrations are now one file, and starting several tasks at once can no longer race on them (#12). The release workflow's last check also says why when the registry refuses a lookup (#11).

Database

• The schema is one migration per dialect, 00001_initial. Migrations 2 and 3 are folded into it, and the schema they build is unchanged.
• On Postgres, startup migrations take an advisory lock, so several tasks starting together migrate one at a time. Before this, two tasks could apply the same migration side by side and one would exit with a duplicate-key error.
• Coming from v0.1.10, delete the records of the folded migrations once v0.1.11 is running, or the next migration numbered 2 will be skipped: DELETE FROM goose_db_version WHERE version_id IN (2, 3);. After that, v0.1.10 can't be redeployed as a rollback.

Releases

• The Verify what was published job asks the registry for each tag's digest directly and reports the registry's own reason when it refuses.