PrintStash v0.7.2: automatic database migrations

PrintStash v0.7.2 removed a fragile manual step from upgrades. Database migrations began running through the image entrypoint before the API starts.

Start the containers and migrate once

Earlier Compose instructions included a separate Alembic command. That command could be removed accidentally while customizing the service, leaving the application and schema out of sync.

The v0.7.2 entrypoint handled three cases on both SQLite and Postgres:

• an Alembic-managed database received pending migrations;
• a fresh database was created at the current schema;
• an existing database with application tables but no Alembic record was adopted without replaying old table-creation migrations.

From this release onward, a normal image upgrade could use docker compose pull followed by docker compose up -d. A backup before upgrading was still required.

Keep browsing context

Deleting a model returned the user to the collection they had been viewing instead of jumping to All Models.

The PrintStash logo also preserved the active collection when returning to the library. Both changes made nested libraries less tedious to clean up.

The current upgrade guide documents the startup migration behavior and recovery checks.