Skip to content

actions: setup/check cache key uses literal version, so version: latest reuses the first downloaded binary #77

Open

Description

@ilanh

Problem

actions/setup and actions/check cache the installed binary with

key: openshell-annotate-${{ runner.os }}-${{ runner.arch }}-${{ inputs.version }}

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

  1. added
    bugSomething is not working
    on Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is not working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions