IntelPython / dpnp / 39993054521

83%

push

github

Pin Miniforge to 26.7.2-1 in GitHub workflows (#3119)

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.

1604 of 2994 branches covered (53.57%)

Branch coverage included in aggregate %.

29404 of 34537 relevant lines covered (85.14%)

17687.67 hits per line