Change workflows to mamba, take 2 #438
Conversation
* Change workflow to mamba
* Fix GitHub Actions * Revert sphinx-multiversion handling
| @@ -26,10 +26,9 @@ dependencies: | |||
| # If versions are updated, also update in `.github/workflows/build_workflow.yml` | |||
| # ================= | |||
| - sphinx=5.2.3 | |||
| - sphinx-multiversion=0.2.4 | |||
There was a problem hiding this comment.
I don't think this matters but using single rather than double = here to match other dependencies.
| # IMPORTANT: This needs to be set for caching to work properly! | ||
| use-only-tar-bz2: true |
There was a problem hiding this comment.
I don't think this is necessary any longer.
There was a problem hiding this comment.
And I think it causes problems because most newer releases are as .conda files.
There was a problem hiding this comment.
This may explain why sphinx-multiversion couldn't be installed.
| # Using pip for Sphinx dependencies because it takes too long to reproduce a conda environment (~10 secs vs. 3-4 mins) | ||
| - name: Install Dependencies |
There was a problem hiding this comment.
This should be much better with mamba instead of conda.
|
@forsyth2 and @tomvothecoder, I think the problem with #429 and #434 were that you did not actually switch to creating a mambaforge environment for building the docs. The environment was still being created with |
|
Unfortunately, we do not have a good way of testing these workflows until we merge this branch and make an |
|
@forsyth2, I think so but I really can't be sure until we actually try a merge and see how it goes. |
|
@forsyth2, it seems like things worked fine so let's proceed with zstash. |
This merge attempts to move all workflows (including building the documentation) to
mambainstead ofpip.