Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

After my conda-forge PR [<https://github.com/conda-forge/staged-recipes/pull/19349|conda-forge#19349>] got meregd, now you have `unionml` available on conda.

LinkedIn Post: `unionml`<https://www.linkedin.com/posts/sugatoray_python-unionml-deployment-activity-6947248533708169216-UCMP?utm_source=linkedin_share&amp;utm_medium=member_desktop_web|  is now on conda-forge>

amazing <@U03LYJNCFB5>! awesome work :tada:

Thank you. Just so you know, I am also one of the maintainers of `flytekit` and `flyteidl` packages on conda-forge. I had to update them to their latest versions for adding `unionml` to conda-forge. So, became a maintainer.

<https://anaconda.org/conda-forge/flytekit>

<https://anaconda.org/conda-forge/flyteidl>

<@U03LYJNCFB5> where’s the recipe hosted?

<@U01DYLVUNJE> The recipe for each conda-forge package is maintained in a GitHub repository, typically referred to as a `feedstock`. This is the general structure of a feedstock URL for a  package on conda-forge.

- `<https://github.com/conda-forge/&lt;package&gt;-feedstock>`

- unionml: <https://github.com/conda-forge/unionml-feedstock>
- flytekit: <https://github.com/conda-forge/flytekit-feedstock>
- flyteidl: <https://github.com/conda-forge/flyteidl-feedstock>

Basically, any dependency of unionml either has to be already present on conda-forge, or one must add them to conda-forge.

This is pretty awesome, <@U03LYJNCFB5>!

Also just so I understand, what's the work involved to bump the package version in each recipe?

I discussed this in a thread before. Please see here: <https://flyte-org.slack.com/archives/C03JL38L65V/p1656379153042659>

Amazing, thank you so much, this answers all my follow up questions as well!