Repository navigation
Pin Miniforge to 26.7.2-1 in GitHub workflows - #3119
Merged
Merged
Conversation
Miniforge3 26.9.4-0 (now `latest`) makes `conda init --all` in
setup-miniconda exit with code 1 on Windows runners ("needs sudo" for
Scripts\conda.exe), so all Windows test jobs fail at conda setup.
antonwolfy
requested review from
ndgrigorian and
vlad-perevezentsev
as code owners
October 23, 2026 15:42
antonwolfy
force-pushed
the
pin-miniforge-version
branch
from
October 23, 2026 15:43
e987da1 to
9fc8b0f
Compare
Contributor
|
Array API standard conformance tests for dpnp=0.21.0dev15=np2py314h8d9cdd5_17 ran successfully. |
ndgrigorian
approved these changes
Oct 23, 2026
Collaborator
|
coverage: 82.62%. remained the same — pin-miniforge-version into master |
tqchen
pushed a commit
to apache/tvm-tirx
that referenced
this pull request
Oct 23, 2026
Windows CI fails with Miniforge 26.9.4-0 during `conda init --all`, reporting `needs sudo` for `Scripts\conda.exe`. The retry then fails because the installation directory is already populated. This pr pins Miniforge to `26.7.2-1` in both the CI setup and wheel publishing actions, including their retry steps, following IntelPython/dpnp#3119.
github-actions Bot
added a commit
that referenced
this pull request
Oct 23, 2026
Miniforge3 [26.9.4-0](https://github.com/conda-forge/miniforge/releases/tag/26.9.4-0) was released on 2026-10-22 and is now what `miniforge-version: latest` resolves to. With it, `conda init --all` inside `conda-incubator/setup-miniconda` exits with code 1 on Windows runners, because it reports `needs sudo` for `Scripts\conda.exe`: ``` needs sudo C:\Users\runneradmin\miniconda3\Scripts\conda.exe ##[error]The process 'C:\Users\runneradmin\miniconda3\condabin\conda.bat' failed with exit code 1 ``` The `ReSetup miniconda` retry step then fails too, because it runs the installer into the already populated directory (`Directory 'C:\Users\runneradmin\miniconda3' is not empty`). As a result, all Windows test jobs of the `Conda package` workflow fail before any test runs, on master (e.g. [run 39971734661](https://github.com/IntelPython/dpnp/actions/runs/39971734661)) and on every PR. The last green run used Miniforge3 26.7.2-1. This PR pins `miniforge-version` to `26.7.2-1` through a workflow-level env variable in every workflow that uses `setup-miniconda`, so the pin can be dropped in one line per workflow once a fixed Miniforge release is available. Linux-only workflows are pinned as well, to keep a single Miniforge version across CI. 1a4a6c6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Miniforge3 26.9.4-0 was released on 2026-10-22 and is now what
miniforge-version: latestresolves to. With it,conda init --allinsideconda-incubator/setup-minicondaexits with code 1 on Windows runners, because it reportsneeds sudoforScripts\conda.exe:The
ReSetup minicondaretry step then fails too, because it runs the installer into the already populated directory (Directory 'C:\Users\runneradmin\miniconda3' is not empty). As a result, all Windows test jobs of theConda packageworkflow fail before any test runs, on master (e.g. run 39971734661) and on every PR. The last green run used Miniforge3 26.7.2-1.This PR pins
miniforge-versionto26.7.2-1through a workflow-level env variable in every workflow that usessetup-miniconda, so the pin can be dropped in one line per workflow once a fixed Miniforge release is available. Linux-only workflows are pinned as well, to keep a single Miniforge version across CI.