From 99274c0bb2e90bcf05ad886385da3a48e7e262c8 Mon Sep 17 00:00:00 2001 From: "H. Vetinari" Date: Sat, 3 Jan 2026 13:54:38 +1100 Subject: [PATCH] update recipe v1 README --- recipes/example-v1/README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/recipes/example-v1/README.md b/recipes/example-v1/README.md index f2a0e51059f33..8c6d589a16261 100644 --- a/recipes/example-v1/README.md +++ b/recipes/example-v1/README.md @@ -1,5 +1,13 @@ # V1 recipe format -This recipe is an example of the v1 recipe format that was defined by [CEP 13](https://github.com/conda/ceps/blob/main/cep-13.md). The v1 recipe format is fully functional when built with rattler-build, but is not yet fully supported by conda-forge's automation. +This recipe is an example of the v1 recipe format that was defined by +[CEP 13](https://github.com/conda/ceps/blob/main/cep-0013.md) and +[CEP 14](https://github.com/conda/ceps/blob/main/cep-0014.md). +The v1 recipe format currently requires rattler-build as a build tool. + +Conda-forge's infrastructure has seen a steady stream of effort to ensure things work as usual with v1 recipes. +As of late 2025, v1 recipes are integrated without any major restrictions. The biggest missing feature is the +lack of [support](https://github.com/conda/ceps/pull/102) for a shared build step between multiple outputs, +though this is not relevant for most recipes. See https://github.com/conda-forge/conda-forge.github.io/issues/2308 for progress on general support for this new format.