-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add user @flying-sheep, update recipe to 1.4 #5
Conversation
@conda-forge/core please merge, @raivivek hasn’t updated this in a while |
@flying-sheep if you send a PR fixing the recipe and adding yourself, it will make it easier for the core members to merge it without waiting for the maintainers. |
I just did that. This is the PR where I add myself. I’m also the maintainer of legacy-api-wrap, so there’s no question if I should be added here or not. |
I'm in automate mode here reading tons of notifications, sorry! |
Actually, it only adds you. Can you update it to 1.3, that is what I meant. Otherwise this is the same as the not one.
Sure, but we have 1-week wait time for the maintainer to answer. IF you update the recipe and add yourself, we can speed up the process and merge it right away. |
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 |
…nda-forge-pinning 2024.03.27.13.43.41
We also need this to be published first: conda-forge/staged-recipes#25877 /edit: huh, for some reason we don’t? |
OK, thank you! |
Checklist