Fix issues with CI tests from upstream changes (#1229)

Author: lrandersson

.github/workflows/main.yml

@@ -111,7 +111,8 @@ jobs:
       - name: Set up conda executable
         run: |
           if [[ "${{ matrix.conda-standalone }}" == "micromamba" ]]; then
-            conda create -yqp "${{ runner.temp }}/micromamba" -c conda-forge micromamba
+            # Pin to <2.6 due to cache regression: https://github.com/mamba-org/mamba/issues/4250
+            conda create -yqp "${{ runner.temp }}/micromamba" -c conda-forge "micromamba<2.6"
             if [[ "${{ runner.os }}" == "Windows" ]]; then
               echo "CONSTRUCTOR_CONDA_EXE=${{ runner.temp }}/micromamba/Library/bin/micromamba.exe" >> $GITHUB_ENV
             else

constructor/winexe.py

@@ -96,7 +96,7 @@ def setup_envs_commands(info, dir_path):
             "no_rcs_arg": info.get("_ignore_condarcs_arg", ""),
         }
     )
-    # now we generate one item per extra env, if present
+    # Now we generate one item per extra env, if present
     for env_name in info.get("_extra_envs_info", {}):
         env_info = info["extra_envs"][env_name]
         # Needed for shortcuts_flags function

dev/environment.yml

@@ -3,6 +3,7 @@ channels:
   - conda-forge
 dependencies:
   - python
+  - pip
   - conda >=4.6
   - ruamel.yaml >=0.11.14,<0.19
   - conda-standalone # >=23.11.0

news/1229-fix-ci-upstream

@@ -0,0 +1,20 @@
+### Enhancements
+
+* <news item>
+
+### Bug fixes
+
+* <news item>
+
+### Deprecations
+
+* <news item>
+
+### Docs
+
+* <news item>
+
+### Other
+
+* CI: Add `pip` to dev environment (required after `conda-libmamba-solver` 26.4.0 enabled sharded repodata by default). (#1229)
+* CI: Pin `micromamba<2.6` due to cache regression ([mamba-org/mamba#4250](https://github.com/mamba-org/mamba/issues/4250)). (#1229)