-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
MNT: rerender #179
base: main
Are you sure you want to change the base?
MNT: rerender #179
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 ( I do have some suggestions for making it better though... For recipe/meta.yaml:
|
…nda-forge-pinning 2024.09.10.07.05.45
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.09.10.07.05.45
Thanks for fixing this. Do we need to set a different build number? I am not sure if a merge will copy over or just drop. |
This was mostly me testing whether the build still passes if we remove the default channels. We don't have to merge this PR, though if you'd like to we can (and then it's safer to bump the build number indeed). Otherwise you can just pick up 56dde22 whenever you do the next PR |
Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #178.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.
Fixes #178