#27100: The pre-migration state used to generate the `AppConfig` exposed through
the `pre_migrate` signal should include already applied migration changes
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: charettes
Type: Bug | Status: closed
Component: Migrations | Version: 1.10
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette <charette.s@…>):
In [changeset:"0b454804db5729eedbb117c90de4a3ad5fb397ee" 0b45480]:
{{{
#!CommitTicketReference repository=""
revision="0b454804db5729eedbb117c90de4a3ad5fb397ee"
[1.10.x] Fixed #27100 -- Included already applied migration changes in the
pre-migrate state.
Refs #24100.
Thanks Tim for the review.
Backport of d5c4ea524679a787fe11c927448e44e95646096b from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27100#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.9f1dfe5dc449410faa556fd73b5e8336%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
