-
-
Notifications
You must be signed in to change notification settings - Fork 1
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 to 0.2.0 #1
Conversation
Needed to change the PyPI link since there was an error with the original release and we had to add a -1 to the tarball.
…nda-forge-pinning 2021.04.09.17.43.25
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 ( |
recipe/meta.yaml
Outdated
url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}.tar.gz | ||
sha256: 552fb15217de85736dc7fea045feccc4c5a4bec3d6b25e617124f6fd633c288f | ||
url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}-1.tar.gz | ||
sha256: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need a checksum here. Also I'm not sure that ver-1 is a pep440 valid version. Maybe we should raise that upstream.
Ah right, I forgot to paste the hash... Thanks for catching that @ocefpaf 🙂 @santisoler maybe we should just release 0.2.1 just to fix these things. |
The |
Let's merge this and see what happens. If there is a problem we can make a new release. |
The bot didn't seem to pick this up so I'm doing it manually. Had to tweak the package URL since we had some trouble with the PyPI release and were forced to add a
-1
to it.Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)