use pixi to publish to conda-forge?

[jgunstone]

currently the workflow I know about to add packages to conda-forge is to add feedstock as described here:
https://conda-forge.org/docs/maintainer/adding_pkgs/

is it possible to use pixi to add conda packages to conda forge? will it be in the future?
when publishing to a different conda channel this seems straightforward to do via GH actions described here:
https://pixi.sh/latest/build/python/
https://prefix.dev/docs/prefix/api
but not sure if the same approach can be taken with conda-forge?

[synapticarbors]

You cannot push packages directly to conda-forge. Everything must go though conda-forge's CI infrastructure, although you can configure it to use the v1 rattler recipe and pixi (https://conda-forge.org/docs/maintainer/conda_forge_yml/#conda-install-tool)

[jgunstone]

ok cool - thanks

I don't that is particular clear from here: https://pixi.sh/latest/build/python/
it would be great if there was an explicit description of the suggested approach when packaging for conda-forge?

in the past I've used grayskull to generate recipes for conda-forge -
if I wanted to do a similar thing within the prefix.dev ecosystem am I right in thinking this is the way to go:
https://rattler.build/latest/recipe_generation/ ?

[synapticarbors]

You can use grayskull with the --use-v1-format flag, or you can use crm convert (https://github.com/conda/conda-recipe-manager). I think grayskull is using crm under the hood. Or you can use rattler. I think crm vs rattler will give you slightly different recipes depending on the package.

[lucascolley]

I would watch #1841, anything further related to this will probably make some noise there.