From 4a7058b85aa678d5e2fefdde7fd483f8261df1c2 Mon Sep 17 00:00:00 2001 From: Henry Schreiner Date: Mon, 20 Jul 2026 12:24:21 -0400 Subject: [PATCH] ci: fix conda-build under setup-miniconda v4 setup-miniconda v4 activates a separate "test" env by default, so conda-build landed there instead of base. Since conda-build is a conda plugin, base's conda no longer saw the 'build' subcommand and the recipe build failed. Install conda-build into base, build for the matrix Python so the artifact ABI matches the test env, and install with --use-local. Drop the unmaintained conda-verify. Assisted-by: ClaudeCode:claude-opus-4.8 --- .github/workflows/conda.yml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/.github/workflows/conda.yml b/.github/workflows/conda.yml index 4110547..9d111a6 100644 --- a/.github/workflows/conda.yml +++ b/.github/workflows/conda.yml @@ -31,14 +31,16 @@ jobs: python-version: ${{ matrix.python-version }} channels: conda-forge + # conda-build is a conda plugin, so it must live in the base env next to + # conda itself (setup-miniconda activates a separate "test" env). - name: Prepare - run: conda install conda-build conda-verify pytest + run: conda install -n base conda-build - name: Build - run: conda build conda.recipe + run: conda build conda.recipe --python=${{ matrix.python-version }} - name: Install - run: conda install -c ${CONDA_PREFIX}/conda-bld/ scikit_build_example + run: conda install --use-local scikit_build_example pytest - name: Test run: pytest tests