You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
actions: setup/check cache key uses literal version, so version: latest reuses the first downloaded binary #77
With version: latest the key is the literal string latest, so the first release downloaded is restored on every later run and newer releases are never installed (until the cache entry is evicted). setup can avoid this with cache: "false", but check has no cache input and always caches.
(Today latest fails anyway because there is no stable release yet, so this bites once v0.1.0 ships.)
Expected
version: latest installs the newest stable release. Options: resolve latest to a concrete tag before the cache step and key on that tag, or skip the cache for latest; add a cache input to check.
Documented as a known issue in docs/GITHUB_ACTIONS.md troubleshooting (#75).
Activity