-
Georges Racinet authored
Heads up: in release branches, the tests are expected to pass for the versions specified in `python/requirements.txt`. Was spotted while working on the Gitaly prebuild, but really has to be fixed: we were running the tests always against the default branch of the Python dependencies (HGitaly and py-heptapod). There is a complication with tags, and especially release branches. For the latter, there is no simple way to know which is the appropriate branch of the Python deps. Shortly after the beginning of the release branch, it would clearly be `default`, but after the swap of branches in the Rails app, it would be `stable`. For tags, the tests are run against the exact versions specified in `python/requirements.txt`, that was easy. For release branches, we just do the same. This is a lesser evil. Hence now, pushes to release branches are expected to make the appropriate version bumps (this was already quite often the case).
bf0b1d7eaa6c