jaimergp

I think conda-build's signing should prevent those errors for you, no need to sign on your own.

Yea, in the long run I'd say we are better off implementing this as one more hook in `conda-pypi`, but for now maybe we can patch it? A workaround would...

Btw, do you have the full traceback @DManowitz?

The logs show no builds 🤔

Ah ok, this is the reason: > One of my dependencies (pyfftw on conda-forge) wasn't installing against Python 3.12 so I limited it to 3.9 - 3.11 for now. The...

> The users are all biologists, many of them rely on scripts from potentially departed lab members for reproducibility This hits close home hah 🫂

> should this be auto-applied to all existing recipes as well ? This can be added as a hint in the linter. Also, not sure if `grayskull` is still defaulting...

I think we are fine with just .org. Given that the equivalent PR in conda-smithy was merged, I'll get this one in too, as is.

I thought [string concatenation](https://docs.rs/minijinja/latest/minijinja/syntax/index.html#other-operators) in (mini)jinja used `~` not `+`

@MikaelUmaN , you are facing https://github.com/conda/conda/issues/12356. Your `--remove` workaround needs to happen _after_ you add the other channel. First append, then remove defaults.