Make chat_backend migrations a single chain #76

Closed
opened 2026-10-18 19:25:49 -07:00 by westfarn · 0 comments
Owner

Two migrations both depend on 0033_agentrun_agentstep:

  • 0034_customuser_use_conversation_context
  • 0034_waitlistentry

makemigrations reports multiple leaf nodes. Make one chain: 0033 → 0034_customuser_use_conversation_context → 0035_waitlistentry.

Do not drop the WaitlistEntry table or model. If 0034_waitlistentry is already recorded in django_migrations, the follow-up is to rename that row to 0035_waitlistentry before migrate.

Two migrations both depend on `0033_agentrun_agentstep`: - `0034_customuser_use_conversation_context` - `0034_waitlistentry` `makemigrations` reports multiple leaf nodes. Make one chain: `0033` → `0034_customuser_use_conversation_context` → `0035_waitlistentry`. Do not drop the WaitlistEntry table or model. If `0034_waitlistentry` is already recorded in `django_migrations`, the follow-up is to rename that row to `0035_waitlistentry` before migrate.
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ai_ml_operations/chat_backend#76