-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update package on conda-forge #26
Comments
Here's the minimum 1.3.6 version needed, waiting on approvals. @tacaswell , @CJ-Wright, @ericdill, @licode - Any of you care to review this 2+ year-old PR? |
Passing review not required, just merge by authorized GH user. |
I think this issue should be closed, we can handle this down-stream. |
How can I release apstools on conda-forge with a non-cf requirement? |
No, I mean this is a problem for us and conda-forge, we should not be bringing the upstream project into this. A core tenant of CF when it started is that upstream maintainers who do not want to work on conda/conda-forge do not have to. This is not their problem and we should not be discussion this in the mongoquery's issues. |
and I got the 1.4.2 PR merged. |
The latest version on conda-forge is 1.3.5. Can you update to a more recent version? At least 1.3.6 is listed in requirements for apstools, part of bluesky.
The text was updated successfully, but these errors were encountered: