summaryrefslogtreecommitdiffstats
path: root/packages/meshbay-hub/src/meshbay_hub/api/users.py
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-08-19 12:19:02 +0200
committerChristophe Besson <cbesson@gmail.com>2026-08-19 12:19:02 +0200
commit9498ce0a34cc363e8cf9a42575c8fcf7dfe0fd1a (patch)
treec4ab47596a33f7de964a10f2b386da7640a6fa99 /packages/meshbay-hub/src/meshbay_hub/api/users.py
parent78711e23e1c200dab28a86d86c1cfa374da9ebbf (diff)
downloadmeshbay-9498ce0a34cc363e8cf9a42575c8fcf7dfe0fd1a.tar.gz
fix(hub): rewrite initial migration to match the ORM models
Six columns (users.pw_version, users.pk_node_ed25519, users.role, groups.description, refresh_tokens.family_id) and two tables (notifications, hub_peers) were never created by migrations — they relied on create_all(), which creates missing tables but never a missing column. This passed every test (fresh SQLite each run) and broke every deploy to a wiped PostgreSQL database. One migration now creates the complete schema. The seven incremental files are removed; their changes are folded into the initial schema. Safe on a fresh database only, which is the only case that exists after the meshbay.org wipe. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Diffstat (limited to 'packages/meshbay-hub/src/meshbay_hub/api/users.py')
0 files changed, 0 insertions, 0 deletions