fix: handle stale Alembic revision on deploy
If the DB has a revision ID that no longer exists in the migration chain (e.g. after a migration history reset), stamp to head then retry upgrade. The retry is a no-op when the schema already matches head.
sha256:17443cc44022f61656614856ed9663c6ac3c3beb957911002ccbdb23143a2726
sha
sha256:4f94d3fa8ec30f41bf1ea3a03339f0db997be371e2a3e3076a06617f03fb95df
snapshot
← Older
Oldest on task/fix-deploy-stale-revision
All commits
Newer →
Latest on task/fix-deploy-stale-revision
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:17443cc44022f61656614856ed9663c6ac3c3beb957911002ccbdb23143a2726 --body "your comment"
No comments yet. Be the first to start the discussion.