The original cache action only supported one scenario; when the step is executed, it looks if there's a cache hit and restores that, and then it automatically adds a second step to the end of the job to save the file location to cache. It also provides a cleaner way to setup caching, as these actions don't need to automatically add a second step to the end of the job (unlike the original cache action). Aside > Aside : It makes little difference to the breaking change that this was a custom action, as users of Github's cache action also need to update.