FIX: Alembic Hotfix

[zdomke]

Description

Fix alembic versioning. #44 accidentally introduced 2 alembic heads.

Just fixing the versioning wasn't enough though as #56 was still preventing the backend from starting up properly. Temporarily remove the auto-updating for alembic.

Users will need to run docker exec squirrel-api alembic upgrade head on a fresh backend build again.

Motivation

Some Alembic issue introduced in #44 & #56.

[shilorigins]

Does fresh backend build include removing volumnes with docker compose down -v?

[zdomke]

Does fresh backend build include removing volumnes with docker compose down -v?

Yes, any time the volumes are removed the users will need to run alembic upgrade again

[shilorigins]

Does fresh backend build include removing volumnes with docker compose down -v?

Yes, any time the volumes are removed the users will need to run alembic upgrade again

Ah, I misunderstood. I thought you meant "for this PR to work then a fresh backend must be built", not "if a fresh backend is built, alembic has to be run"

[shilorigins]

For clarity, I ran docker compose down && docker compose up -d --build on my existing instance and it's working without issue.

[shilorigins]

This seems to work for me, so let's get it merged in.

[zdomke]

Realizing that I shouldn't have manually changed the values for Revises and down_revision. I should have instead run alembic merge heads and committed the merge revision. This is good to know for future use.

I may also want to spend some time learning how to properly use alembic.