public/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-10-04 22:03:39 +09:00
Code Issues Packages Projects Releases Wiki Activity

db: drop migrations predating 0.29

Browse Source 
Only 0.29.x -> 0.30 upgrades are supported; checkMinimumMigration refuses
older databases instead of silently skipping the removed steps.
This commit is contained in:
Kristoffer Dalby
2026-09-23 16:11:51 +00:00
committed by Kristoffer Dalby
parent 04d1e3c83f
commit e90500e3a9
19 changed files with 216 additions and 1471 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+5 -7
View File
@@ -185,19 +185,17 @@ headscale/
## Database Migration Rules
These rules are load-bearing — violating them corrupts production
databases. The `migrationsRequiringFKDisabled` map in
`hscontrol/db/db.go` is frozen (see the comment above it). All new
databases. Migrations start at 0.29.0; `checkMinimumMigration` in
`hscontrol/db/versioncheck.go` refuses older databases. All new
migrations must:
1. **Never reorder existing migrations.** Migration order is immutable
once committed.
2. **Only add new migrations to the end** of the migrations array.
3. **Never disable foreign keys.** No new entries in
`migrationsRequiringFKDisabled`.
3. **Never disable foreign keys.**
4. **Use the migration ID format** `YYYYMMDDHHMM-short-description`
(timestamp + descriptive suffix). Example: `202602201200-clear-tagged-node-user-id`.
5. **Never rename columns** that later migrations reference. Let
`AutoMigrate` create a new column if needed.
(timestamp + descriptive suffix). Example: `202607241200-clear-tagged-node-expiry`.
5. **Never use `AutoMigrate`** in a migration; write explicit DDL.
## Tags-as-Identity