update GitHub Actions to use miniforge v3 (fixes mambaforge deprecation) #1079
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.
Mambaforge support in Miniconda is being deprecated since mamba is now included directly in miniforge, as described here. To "encourage users to switch to Miniforge" a set of "brownouts" has been scheduled at increasing frequency, and one of them happened today, causing GitHub Actions workflows to stop working.
This PR updates the GitHub Actions workflows to use miniconda@v3, which fixes the issue.
Note: there are still some failures in the OS/BLAS test matrix workflow for Intel-based MacOS (example). I'm not sure these are directly related to miniforge/mamba since they appear to affect only certain configurations in the test matrix. I'll post a separate issue on that one.