From dbbe2b63f49354482a5e3d0021ca2b8b541b5b4b Mon Sep 17 00:00:00 2001 From: Alex Hedges Date: Sat, 24 Feb 2024 21:55:22 -0500 Subject: [PATCH] Skip check for miniforge version `4.13.0-0` We always detect missing build scripts for `4.13.0-0` because the release[^1] doesn't have any mambaforge artifacts. Given that we've already created the build files, we don't need to check the release again. [^1]: https://github.com/conda-forge/miniforge/releases/tag/4.13.0-0 --- plugins/python-build/scripts/add_miniforge.py | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/plugins/python-build/scripts/add_miniforge.py b/plugins/python-build/scripts/add_miniforge.py index efa17a91..741ead90 100755 --- a/plugins/python-build/scripts/add_miniforge.py +++ b/plugins/python-build/scripts/add_miniforge.py @@ -100,6 +100,11 @@ for release in requests.get(f'https://api.github.com/repos/{MINIFORGE_REPO}/rele logger.info('Looking for %(version)s in %(out_dir)s', locals()) + # Release has no mambaforge artifacts, which causes the next check to always trigger + # Build scripts have already been generated, so safe to skip this version + if version == '4.13.0-0': + continue + if any(not list(out_dir.glob(f'{distribution}*-{version}')) for distribution in DISTRIBUTIONS): logger.info('Downloading %(version)s', locals()) add_version(release)