{"push_id":1096647969,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ac3bbca051c5b87ddbe7cc1a477be013b0669f12","before":"cca71a5774605467ab7995b005a2db9e7a2be81b","commits":[{"sha":"ac3bbca051c5b87ddbe7cc1a477be013b0669f12","author":{"email":"976bdec73968f87717846abb5bf1f2a1037e80c6@rackspace.co.uk","name":"Jesse Pretorius"},"message":"Change pip install task state to 'latest'\n\nCurrently all pip install tasks only require the package to be\npresent. This means that when an environment undergoes a minor\nupgrade the package is not upgraded to the same version that\nwas tested with. This ultimately results in a deployed\nenvironment that does not match the tested environment.\n\nWhile for the services installed into venvs this is not an\nissue, it does affect those which do not use venvs and any\npackages which are installed outside of a venv or on top\nof a venv.\n\nThis patch changes the behaviour to ensure that the install\ntask will always use the latest available package. In\ndeveloper_mode this will mean using the version specified\nin upper-constraints, and in an integrated build this will\nmean the version which is available in the wheel repo's\nfolder for the tag.\n\nChange-Id: I90a044e142829ea90bbc81cdda5a2a257fe8de22","distinct":true,"url":"https://api.github.com/repos/openstack/openstack-ansible-galera_server/commits/ac3bbca051c5b87ddbe7cc1a477be013b0669f12"}]}