Test

.github/workflows/caching-example.yml

@@ -23,7 +23,7 @@ jobs:
         with:
           path: ~/conda_pkgs_dir
           key: ${{ runner.os }}-conda-${{ env.CACHE_NUMBER }}-${{ hashFiles('etc/example-environment.yml') }}
-      - uses: goanpeca/setup-miniconda@check-cache
+      - uses: goanpeca/setup-miniconda@1.x
         with:
           activate-environment: anaconda-client-env
           python-version: 3.8

README.md

@@ -9,7 +9,7 @@ This action sets up a [Miniconda](https://docs.conda.io/en/latest/miniconda.html
 
 Miniconda `condabin/` folder is added to `PATH` and conda is correctly initialized across all platforms.
 
-This action correctly handles activation of conda environments and offers the possibility of automatically activating the test environment on all shells. 
+This action correctly handles activation of conda environments and offers the possibility of automatically activating the test environment on all shells.
 
 See the **[IMPORTANT](#IMPORTANT)** notes on additional information on environment activation.
 
@@ -218,13 +218,15 @@ jobs:
           python-version: 3.8
           channel-priority: strict
           environment-file: etc/example-environment.yml
+          use-only-tar-bz2: true  # IMPORTANT: This needs to be set for caching to work properly!
 ```
 
 ## IMPORTANT
 
 - Bash shells do not use `~/.profile` or `~/.bashrc` so these shells need to be explicitely declared as `shell: bash -l {0}` on steps that need to be properly activated. This is because bash shells are executed with `bash --noprofile --norc -eo pipefail {0}` thus ignoring updated on bash profile files made by `conda init bash`. See [Github Actions Documentation](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#using-a-specific-shell) and [thread](https://github.community/t5/GitHub-Actions/How-to-share-shell-profile-between-steps-or-how-to-use-nvm-rvm/td-p/33185).
 - Sh shells do not use `~/.profile` or `~/.bashrc` so these shells need to be explicitely declared as `shell: sh -l {0}` on steps that need to be properly activated. This is because sh shells are executed with `sh -e {0}` thus ignoring updated on bash profile files made by `conda init bash`. See [Github Actions Documentation](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#using-a-specific-shell).
 - Cmd shells do not run `Autorun` commands so these shells need to be explicitely declared as `shell: cmd /C call {0}` on steps that need to be properly activated. This is because cmd shells are executed with `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""` and the `/D` flag disabled execution of `Command Processor/Autorun` windows registry keys, which is what `conda init cmd.exe` sets. See [Github Actions Documentation](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#using-a-specific-shell).
+- For caching to work properly, you will need to set the `use-only-tar-bz2` option to `true`.
 
 # License