Question

Your platform team maintains a reusable workflow in the repo `acme/ci-shared` at `.github/workflows/deploy.yml`. A consuming repository invokes it like this:

```yaml
jobs:
  ship:
    uses: acme/ci-shared/.github/workflows/deploy.yml@v2
    secrets: inherit
```

The platform team just pushed a bug fix to the `main` branch of `acme/ci-shared` but has NOT moved or recreated the `v2` tag. A developer reports the consuming repo's runs still execute the old, buggy logic. What is the correct explanation?

Accepted Answer

The `uses` reference resolves the reusable workflow at the `v2` git ref, so the consumer keeps running the code the tag points to until `v2` is updated to include the fix.

Answer

Reusable workflows always execute the version on the caller's default branch, so the consumer must merge the fix into its own repository first.

Answer

`secrets: inherit` caches the reusable workflow definition, so clearing the caller's Actions cache will pull in the fixed version.

Answer

Reusable workflows are copied into the consumer at invocation time like a starter workflow, so the consumer must re-scaffold the workflow to get the fix.