{"push_id":2387765851,"size":1,"distinct_size":1,"ref":"refs/heads/stable/2.0.x","head":"0fd21febe7b3969460e3e6f17bfedc63529f194b","before":"8d3bd724ab996078a570dd736b85a8ad5b317f97","commits":[{"sha":"0fd21febe7b3969460e3e6f17bfedc63529f194b","author":{"name":"Simon Charette","email":"832e4a067ae67c416bee18fcd93d112e7838db32@gmail.com"},"message":"[2.0.x] Fixed #29195 -- Fixed Exists.output_field resolution on single-valued queries.\n\nThe Subquery class which Exists inherits from defaulted to using single-valued\nquerie's field if no output_field was explicitly specified on initialization\nwhich was bypassing the Exists.output_field defined at the class level.\n\nMoving Subquery's dynamic output_field resolution to _resolve_output_field\nshould make sure the fallback logic is only performed if required.\n\nRegression in 08654a99bbdd09049d682ae57cc94241534b29f0.\n\nThanks Oli Warner for the detailed report.\n\nBackport of 277ed072094ad87fc6b2c4669f21d43b1f39043c from master","distinct":true,"url":"https://api.github.com/repos/django/django/commits/0fd21febe7b3969460e3e6f17bfedc63529f194b"}]}
{"actor":{"display_login":"timgraham"}}