# Django 4 migrations #371
mpeltriaux
commented 2023-12-12 07:34:33 +01:00
Owner
- migrations created because of switch to Django4
* migrations created because of switch to Django4
mpeltriaux
added 1 commit 2023-12-12 07:34:34 +01:00
# Django 4 migrations
29a55c9427
mpeltriaux
merged commit 96d2b5aa6c into master 2023-12-12 07:34:41 +01:00
mpeltriaux
deleted branch django_4_migrations 2023-12-12 07:34:41 +01:00
mpeltriaux
referenced this issue from a commit 2023-12-12 07:34:41 +01:00
Merge pull request '# Django 4 migrations' (#371) from django_4_migrations into master
btuelek
referenced this issue from a commit 2024-12-05 13:18:39 +01:00
Merge pull request '# Django 4 migrations' (#371) from django_4_migrations into master
No reviewers
Labels
No Label
backlog
bug
duplicate
enhancement
feature
help wanted
invalid
question
wontfix
bug
duplicate
enhancement
help wanted
in discussion
invalid
priority
1
priority
2
priority
3
priority
4
priority
5
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: IT-Naturschutz/konova#371
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "django_4_migrations"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?