From c52f4295f254e1c14af769d22b1a5f516a941f58 Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Wed, 17 May 2023 13:14:43 +0200 Subject: Fixed #34568 -- Made makemigrations --update respect --name option. Thanks David Sanders for the report. --- docs/ref/django-admin.txt | 3 +++ docs/releases/4.2.2.txt | 3 +++ 2 files changed, 6 insertions(+) (limited to 'docs') diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index d268d88e80..110b1e802a 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -757,6 +757,9 @@ generated migration files to ``stdout``. Merges model changes into the latest migration and optimize the resulting operations. +The updated migration will have a generated name. In order to preserve the +previous name, set it using ``--name``. + ``migrate`` ----------- diff --git a/docs/releases/4.2.2.txt b/docs/releases/4.2.2.txt index ca21e5f1ec..7506b8a237 100644 --- a/docs/releases/4.2.2.txt +++ b/docs/releases/4.2.2.txt @@ -19,3 +19,6 @@ Bugfixes * Fixed a regression in Django 4.2 that caused a crash of ``QuerySet.defer()`` when passing a ``ManyToManyField`` or ``GenericForeignKey`` reference. While doing so is a no-op, it was allowed in older version (:ticket:`34570`). + +* Fixed a bug in Django 4.2 where :option:`makemigrations --update` didn't + respect the ``--name`` option (:ticket:`34568`). -- cgit v1.2.1