From fc3e89edd298d5f20a031d92e36f7fe36c484558 Mon Sep 17 00:00:00 2001 From: Lorenzo Gaifas Date: Thu, 2 Oct 2025 10:28:50 +0200 Subject: [PATCH 1/2] add info about manual trigger of conda update --- docs/developers/coredev/release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developers/coredev/release.md b/docs/developers/coredev/release.md index de7bcf3ed..37be7da1c 100644 --- a/docs/developers/coredev/release.md +++ b/docs/developers/coredev/release.md @@ -245,7 +245,7 @@ For a more complete description of the napari packaging infrastructure, see {ref ### New releases -Once the PyPI release is available, the `conda-forge` bots will submit a PR to `conda-forge/napari-feedstock` within about twelves hours. The release manager may not have push/merge rights to the feedstock, so ask a recipe maintainer for assistance. Merging the bot PR to `main` will trigger the `conda-forge` release. +Once the PyPI release is available, the `conda-forge` bots will submit a PR to `conda-forge/napari-feedstock` within about twelves hours. Alternatively, to speed up the process, you may open an issue [following the version update instructions in this template](https://github.com/conda-forge/napari-feedstock/issues/new?template=2-bot-commands.yml) to manually trigger the update. The release manager may not have push/merge rights to the feedstock, so ask a recipe maintainer for assistance. Merging the bot PR to `main` will trigger the `conda-forge` release. Accounting for the build times and the CDN sync, this means that the `conda-forge` packages will be available 30-60 mins after the PR is merged. Before merging, please pay special attention to these aspects: From 374b359497db3a376e0dc33ec85f854ecd6f3200 Mon Sep 17 00:00:00 2001 From: Lorenzo Gaifas Date: Mon, 6 Oct 2025 10:27:21 +0200 Subject: [PATCH 2/2] Update docs/developers/coredev/release.md Co-authored-by: Tim Monko --- docs/developers/coredev/release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developers/coredev/release.md b/docs/developers/coredev/release.md index 37be7da1c..4e9e55fe0 100644 --- a/docs/developers/coredev/release.md +++ b/docs/developers/coredev/release.md @@ -245,7 +245,7 @@ For a more complete description of the napari packaging infrastructure, see {ref ### New releases -Once the PyPI release is available, the `conda-forge` bots will submit a PR to `conda-forge/napari-feedstock` within about twelves hours. Alternatively, to speed up the process, you may open an issue [following the version update instructions in this template](https://github.com/conda-forge/napari-feedstock/issues/new?template=2-bot-commands.yml) to manually trigger the update. The release manager may not have push/merge rights to the feedstock, so ask a recipe maintainer for assistance. Merging the bot PR to `main` will trigger the `conda-forge` release. +Once the PyPI release is available, the `conda-forge` bots will submit a PR to `conda-forge/napari-feedstock` within about twelves hours. Alternatively, to speed up the process, you may open an issue with title [`@conda-forge-admin, please update version`](https://github.com/conda-forge/napari-feedstock/issues/new?template=2-bot-commands.yml) to manually trigger the bot. The release manager may not have push/merge rights to the feedstock, so ask a recipe maintainer for assistance. Merging the bot PR to `main` will trigger the `conda-forge` release. Accounting for the build times and the CDN sync, this means that the `conda-forge` packages will be available 30-60 mins after the PR is merged. Before merging, please pay special attention to these aspects: