edgeandnode/Setup Amp
Install Amp (`ampd`, `ampctl`, `ampsql`) in CI via ampup, with version pinning and caching of the ampup-managed install directory.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 6, 2026
- License
- None
Pinned Snippet
uses: edgeandnode/setup-amp@977032beba349f9b668299169227548ebf116794 # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| version | Amp version to install. Accepts `stable` (the latest stable release), `latest` (an alias for `stable`), `nightly` (the most recent nightly release), or an explicit release tag such as `v0.0.36` or `nightly-425b88a`. Use `none` to install only `ampup` itself, without installing any Amp version (no `ampd`/`ampctl`/`ampsql`). This skips version resolution and caching, and requires no GitHub token. | no | stable |
| github-token | GitHub token used to resolve versions and download release assets from the Amp repository. While the Amp repository is private, this must be a token with read access to `edgeandnode/amp` releases. The default workflow token only has access to the repository running the workflow, so workflows in other repositories must pass a GitHub App or PAT token here. | no | ${{ github.token }} |
| cache | Whether to cache the ampup-managed install directory across runs. Caching is enabled by default. The cache is saved by a post step at the end of a successful job, and restored before installing. | no | true |
| cache-key | Custom cache key to use instead of the automatic `setup-amp-<repo>-<platform>-<arch>-<resolved version>` key. Note that overriding the key removes the resolved version from the cache identity; the action still converges on the requested version by running `ampup install` after a restore. | no | "" |
| cache-restore-keys | Additional cache restore keys (one per line), used to restore a partially matching cache when no exact key match exists. A partial restore avoids re-downloading `ampup` itself; the requested Amp version is still installed on top of the restored directory. | no | "" |
Outputs
| name | description |
|---|---|
| version | The installed Amp version as a release tag (e.g. `v0.0.36` or `nightly-425b88a`), after resolving `stable`, `latest`, or `nightly`. |
| cache-hit | Whether the ampup install directory was restored from an exact cache key match. `false` when caching is disabled. |