Looks good! Is it draft on purpose or I can merge it?

@aviramha sorry for the delay in replying! There are two things left imo:

• In my own tests I ran into an error that said Error getting latest release: 403 rate limit exceeded. I'm going to see if I can reproduce this. I wonder if a GITHUB_TOKEN needs to be passed to the action?
  • If we need to use a token, the blue "Important" box here makes it sound like we can pick it up without the action user actually passing a token 🤔
• I don't want to increase the scope of this PR if possible, but I'm wondering how the caching of the sccache binary should be handled. Should we always check if the latest version is in the cache and if not, we download it and cache it? Alternatively we could check the cache for any version greater than or equal to the last known working version and use that
  • If we go with the second approach and a bug arises in the version that's in the cache, should the action user have a way of forcing the action to download and use a specific version of sccache?
  • A side question — is the tool cache only actually used on self-hosted runners? If that's the case I wonder how we can test this behavior if we're using the GitHub-hosted runners 🤔

I'll look into the first point but I was wondering what your thoughts are on the second one

Either approach looks good ;)