Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
@conda-forge-admin, please rerender |
|
There is a failure: |
|
Yes, it's due to #66 (comment) maybe I shouldn't have re-rended. Will remove the last commit and see if it helps.. |
This reverts commit c5f7b58.
recipe/meta.yaml
Outdated
|
|
||
| build: | ||
| number: 201 | ||
| number: 0 |
There was a problem hiding this comment.
So this needs to be 200.
There was a problem hiding this comment.
We could also use this trick ( conda-forge/numpy-feedstock@4a98d05 ).
There was a problem hiding this comment.
Thanks for the review! Set it to 200, I think it's still more explicit that setting then incrementing the build_number variable..
This tests the upcoming 0.19.2 release can be built without errors. Do not merge.Packages the 0.19.2 release