Ed Morley
Ed Morley
Another option would be to allow previewing the changes as part of the workflow, similar to manually pasting the requirements file into https://pyup.io/tools/requirements-checker/ and seeing what gets updated.
We run `pip check` in our Travis run so CI fails in this case, see: https://github.com/PyCQA/pycodestyle/issues/741#issuecomment-380261935 I guess pyup could do the same (run `pip check`), however I wonder what's...
Thank you for your work on this! > The bot won't respect ranges set in a Pipfile when updating the Pipfile.lock. Unfortunately this is a blocker for us, since we...
Ah it was the PR title change not the rebase? I was presuming it would have used the pull request number rather than the title, or given the message "Close...
Ah I didn't realise that was not currently possible. Looking at the warehouse (PyPI replacement) tracker I see there is an issue open for a related feature: pypa/warehouse#1683 Until that's...
The aiohttp 2.3.3 update broke us again. I think perhaps #262 is a more viable alternative to this idea for now?
Yeah that would work too :-)
Thank you for adding the delay, though I think sadly 2 hours might not be enough for aiohttp. For example, this PR doesn't have the manylinux1 hash: https://github.com/mozilla/treeherder/pull/3003 ...so now...
This just bit us for [pycryptodome](https://github.com/Legrandin/pycryptodome) in mozilla/treeherder/pull/3320
Is the bot and the site using a different requirements file parser perhaps, and the site one not accounting for the newlines?