Description

The save-always input added in v4 is not working as intended due to post-if expressions not supporting the input context.

To avoid breaking users who have already added this input to their workflows, it is being deprecated now and will be removed in the next major version (v5).

This also fixes our documentation for how to properly use the recommended alternative of a separate actions/cache/save step, which requires checking the cache-hit output to avoid attempting to save a cache that already exists.

Motivation and Context

• v4.0 save always not working #1315
• if: always() with cache/save may lead to errors (fix README!) #1154

How Has This Been Tested?

Validated that the input had a deprecation message: https://github.com/joshmgross/actions-testing/actions/runs/10395133356

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (add or update README or docs)

Since save-always is already broken, I do not consider this a breaking change.

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.