From 4d1ea5e1bb7a13fd2af11ad1856fd4039d02e7a4 Mon Sep 17 00:00:00 2001 From: Matthew Feickert Date: Mon, 11 Nov 2024 22:46:13 -0700 Subject: [PATCH] DOC: Add note on patch deployment to anaconda.org * Note that after a PR is merged there are no further actions for anyone to take on the conda-forge side and that Anaconda is responsible for the automation infrastructure of applying the patches to distributions on https://anaconda.org/conda-forge/. --- recipe/README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/recipe/README.md b/recipe/README.md index 58ec5c1bf..cd99d71d7 100644 --- a/recipe/README.md +++ b/recipe/README.md @@ -234,3 +234,9 @@ instructions = { A tool downloads this package when it sees updates to it, and applies the `patch_instructions.json` to the repodata of the `conda-forge` channel on anaconda.org + +## Deployment of patches to `anaconda.org` + +After a patch PR is merged there are no further actions for patch submitters, feedstock maintainers, or conda-forge to take. +Anaconda, Inc. manages the infrastructure that applies patches from this repository to the repodata of distributions on [anaconda.org/conda-forge/](https://anaconda.org/conda-forge/). +This infrastructure is related to the process for updating their CDN, so patches should generally be applied and usable within a few hours after a patch PR is merged.