{"push_id":1174641927,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"bd52b0c6c7b5cde9f0e26b70d012e7617fbcd8ea","before":"2500cb337c709a37fc77fdf2ac2a1052a6f2fc38","commits":[{"sha":"bd52b0c6c7b5cde9f0e26b70d012e7617fbcd8ea","author":{"name":"Paul Millar","email":"4a6a3bb8c9d01f48480af5e8f6480cef5e8e3747@desy.de"},"message":"Add support for a --no-push option\n\nWhen making security-related releases, we want to do all release-tagging\nrelated activity locally, without exposing the actual change.  This is\nto support a \"binary-only\" release to give admins the opportunity to\ninstall the upgrade without making details of the vulnerability public.\n\nOne an embargo period is over, the local changes may be pushed to\ngithub.\n\nCare must be taken that this does not trigger the usual build process,\nas this will result in packages with different checksum values.","distinct":true,"url":"https://api.github.com/repos/dCache/release-utils/commits/bd52b0c6c7b5cde9f0e26b70d012e7617fbcd8ea"}]}
{"actor":{"display_login":"paulmillar"}}