Releases: spack/setup-spack
Releases · spack/setup-spack
v3.0.0
Breaking Changes
This release adds support for Spack v1.x and removes support for Spack v0.x.
Action Required: Update your workflows to use the new input names:
ref->spack_refrepository->spack_repositorypath->spack_path
New features
- Separate package repository support: automatically clones and configures both
spack/spack(tool) andspack/spack-packages(packages). - Separate pinning of tool and packages: set
spack_refandpackages_refindependently to use specific versions of the tool and packages - Fork support: test your own Spack or packages forks with
spack_repositoryandpackages_repositoryinputs
Migration Example
Before (v2.x):
- uses: spack/setup-spack@v2
with:
ref: developAfter (v3.x):
- uses: spack/setup-spack@v3
with:
spack_ref: developv2.1.1
- For Spack
v0.22.0.dev0and higherspack installwithout further flags can
install prebuilt binaries from the build cache without erroring about missing
signatures on the binaries. The default build cache is marked as "unsigned". - Disable
/etc/spackand~/.spackconfig files, only use$spack/etc
v2.1.0
- Support shell aware commands like
spack env activateandspack loadin thespack-bash
andspack-shshells.
v2.0.1
v2.0.0
Major update to this action:
- Enable the build cache from https://github.com/spack/github-actions-buildcache
- Enable color by default
Other changes:
- Removed custom bootstrapped binaries for clingo
- Removed option for choosing the concretizer
v1.2.1
Minor docs improvements
v1.2.0
Allows you to enable/disable the new concretizer with concretizer: clingo and concretizer: original resp.