Potential for cache key conflicts with reusable workflows

[omus]

The julia-actions/cache action attempts to generate a unique cache key name for each workflow job. The current default key uses a combination of the workflow name, job key, matrix keys, run ID, and run attempt to achieve this.

If a user makes use of a reusable GHA workflow it is possible that the triggering workflow and the reusable workflow could both use julia-actions/cache and the same job key resulting in a cache key conflict (as demonstrated here: https://github.com/julia-actions/cache/pull/160#issuecomment-2610836773).

[omus]

The obvious solution would be to add the reusable workflow name and possibly the inputs to the key to ensure things are distinct. However, accessing the workflow name from within the reusable workflow returns the triggered workflow and not the reusable one.

[giordano]

Yes, I'm also having the same problem

[giordano]

For the record, manually setting the cache-name to include all the relevant disambiguation values helps.