{"push_id":766862096,"size":4,"distinct_size":4,"ref":"refs/heads/23727","head":"6c2bbfcc674e6350b6c680b37c7b423177847906","before":"7acd338929cafc8c1059f0aac3b6405678a6b009","commits":[{"sha":"d3bc86ec11bb22f06b5e30fac891ef3e43f82a6d","author":{"email":"7d64dbc04187ef4ff3002b119b8edfcfccfa8892@gmail.com","name":"Tim Graham"},"message":"Fixed #25284 -- Documented removal of implicit QuerySet __in lookups.","distinct":true,"url":"https://api.github.com/repos/timgraham/django/commits/d3bc86ec11bb22f06b5e30fac891ef3e43f82a6d"},{"sha":"97ac77e544f9b1d1f28c0f859bef8fbc195d81a5","author":{"email":"7d64dbc04187ef4ff3002b119b8edfcfccfa8892@gmail.com","name":"Tim Graham"},"message":"Removed BaseForm._raw_value().\n\nUnused since efb0100ee67931329f17bc9988ecd5f0619cea14.","distinct":true,"url":"https://api.github.com/repos/timgraham/django/commits/97ac77e544f9b1d1f28c0f859bef8fbc195d81a5"},{"sha":"26dcf739eaf5577c5072eb8c9ba1c5ac5605683f","author":{"email":"7d64dbc04187ef4ff3002b119b8edfcfccfa8892@gmail.com","name":"Tim Graham"},"message":"Forwardported release note for refs #25040.","distinct":true,"url":"https://api.github.com/repos/timgraham/django/commits/26dcf739eaf5577c5072eb8c9ba1c5ac5605683f"},{"sha":"6c2bbfcc674e6350b6c680b37c7b423177847906","author":{"email":"b82b779e6a897928855f4bd14cab2fe6cafcf6de@arbor.net","name":"Tommy Beadle"},"message":"Fixed #23727 -- Inhibited the post_migrate signal when using serialized_rollback.\n\nWhen using a TransactionTestCase with serialized_rollback=True,\nafter creating the database and running its migrations (along with\nemitting the post_migrate signal), the contents of the database\nare serialized to _test_serialized_contents.\n\nAfter the first test case, _fixture_teardown() would flush the\ntables but then the post_migrate signal would be emitted and new\nrows (with new PKs) would be created in the django_content_type\ntable. Then in any subsequent test cases in a suite,\n_fixture_setup() attempts to deserialize the content of\n _test_serialized_contents, but these rows are identical to the\nrows already in the database except for their PKs.  This causes an\nIntegrityError due to the unique constraint in the\ndjango_content_type table.\n\nThis change made it so that in the above scenario the post_migrate\nsignal is not emitted after flushing the tables, since it will be\nrepopulated during fixture_setup().","distinct":true,"url":"https://api.github.com/repos/timgraham/django/commits/6c2bbfcc674e6350b6c680b37c7b423177847906"}]}