This is related to the other issue you linked. Our devops team is investigating how best to solve this for future releases.