In my experience, people often have some questions about conda-forge packaging. I have tried to put together some FAQ's in the discussions under UnionML repository. I hope this helps in future. • https://github.com/unionai-oss/unionml/discussions/137

@happy-river-91250 did you add flytekit to conda too?

@freezing-airport-6809 I updated

flytekit

and

flyteidl

from their older versions to the latest ones on conda-forge. Was necessary for adding

unionml

. So, currently I am the maintainer of all three packages on conda-forge.

Ohh but we do not have an auto publish for flytekit and flyteidl

conda-forge does not allow auto publish

Ohh really

In short: if no new dependency was added to the code base, then right after a PyPI release, there is a conda-forge bot that will create an update package. But if dependencies change, or the indirect dependencies change, then you might need manual intervension -- like it was necessary this time. Ideally, the maintainer will upgrade the package. But PRs are welcome. Once a PyPI release happens, please raise an issue at the feedstock or send a PR.

Cc @thankful-minister-83577 the e should this to readme

we should also create a

flytekitplugins

conda package where we maintain all the first-party plugins. We can create a recipe that publishes all plugins in one. See the

pandera

recipe as an example: https://github.com/pandera-dev/pandera-feedstock/blob/master/recipe/meta.yaml

i think that makes sense if that’s alright with you @happy-river-91250

created this issue: https://github.com/flyteorg/flyte/issues/2636 @happy-river-91250 let me know if you’d by down to make a contribution on this front!

also, we’re going to be cutting the next flytekit release later this week or early next, mind walking through any steps there are to do sugato? and then maybe I can document them?

@broad-monitor-993 that would be great to become co maintainers

About becoming co-maintainers: I will be glad to add some people. But let's only add people as co-maintainers, once they have updated a recipe and better yet once they have created a new conda-forge recipe. So, let's take steps toward sending PRs first to the feedstocks. Let's first get you more comfortable with fixing all build errors, and if necessary, creating newer recipes. But, I appreciate this discussion of having more co-maintainers. 👏 cc: @broad-monitor-993 @freezing-airport-6809 @thankful-minister-83577

thanks.

@thankful-minister-83577 Please let me know if any other changes are necessary in the PR.

hey sorry i forgot to respond

Thank you. I will look into it.