Description

I've noticed a bug in the Phive install action where the cache key is incorrectly calculated. Instead of generating a hash from phars.xml, the function name is printed as a string, leading to cache failures when phars.xml is updated in a single pull request.

Current Output:

Fix:
I updated the cache key calculation from:

key: "phive-hashFiles('**/phars.xml')"

to:

key: phive-${{ hashFiles('**/phars.xml') }}

After fix is applied:

This should ensure the correct hash is generated and the cache is restored properly.

I encountered a similar issue in my wayofdev/gh-actions repository, which also uses Phive install inspired by your repository.

How to check cache keys?:

https://github.com/cli/cli can be used to check all cache keys of repository:

gh cache list