Ed Morley
Ed Morley
Hi! pyup currently has a `schedule` config option ([docs](https://pyup.io/docs/bot/config/#schedules)), which allows for the batching up of updates into one periodic PR. This has the following advantages: 1. Fewer email/IRC/... "PR...
Hi! This PR is now showing as having conflicts in the requirements file, since another pyup PR was merged that changed lines near to those being updated: https://github.com/mozilla/treeherder/pull/3404 However the...
**STR:** 1) Add https://github.com/mozilla/treeherder to pyup.io 2) Wait for the initial PR test to complete 3) Notice that one of the updates causes a test failure (in this case, isort...
I had read the pyup docs and so knew we'd need to add filters to our requirements files, since not all packages are safe to update (eg Celery 4 causes...
Hi! In our requirements file ([here](https://github.com/mozilla/treeherder/blob/f0940ec37d36de08e8a067f8d1778ab008bb5de0/requirements/common.txt#L0)), we have several packages that have `# pyup:` annotations pinning them to an older range: ``` celery==3.1.25 \ --hash=sha256:1954a224805f3835e5b6f5998ec9fe51db3413cc49e59fc720d314c7913427cf \ --hash=sha256:6ced63033bc663e60c992564954dbb5c84c43899f7f1a04b739957350f6b55f3 # pyup:
Hi! For projects that use hashes in their requirements files, pyup-bot's PR includes the hashes for all available files at the time the PR was open. However if additional package...
pyup-bot's initial PR updated `pytest-html` from 1.13.0 to 1.14.2. The new version has apparently added a dependency on `pytest-metadata`, which means the Travis run failed with: ``` In --require-hashes mode,...
Recent Travis runs are showing: ``` npm WARN deprecated [email protected]: This loader has been deprecated. Please use eslint-webpack-plugin ``` It appears that eslint-loader has been deprecated in favour of eslint-webpack-plugin:...
Yarn has a new experimental and opt-in mode called "Plug n Play" that means packages are no longer installed into `node_modules` and are instead mapped to their cache location at...
Hi! Thank you for a great tool :-) I'm currently experiencing `cargo watch -x test` looping indefinitely, with `--why` reporting that the cause is a file that hasn't been modified...