The save action saves a cache. It works similarly to the cache action except that it doesn't first do a restore. This action provides granular ability to save a cache without having to restore it, or to do a save at any stage of the workflow job -- not only in post phase.

• key - An explicit key for a cache entry. See creating a cache key.

• path - A list of files, directories, and wildcard patterns to cache. See @actions/glob for supported patterns.

• upload-chunk-size - The chunk size used to split up large files during upload, in bytes

• enableCrossOsArchive - An optional boolean when enabled, allows windows runners to save caches that can be restored on other platforms. Default: false

• enableCrossArchArchive - An optional boolean when enabled, allows runners of different architectures to save caches that can be restored on other architectures. Default: false

  Note: GitHub's actions/cache does not have this option and allows cross-architecture caching by default. In WarpCache, cross-architecture support requires explicitly setting enableCrossArchArchive: true.

This action has no outputs.

If you are using separate jobs for generating common artifacts and sharing them across jobs, this action will take care of your cache saving needs.

steps:
  - uses: actions/checkout@v6

  - name: Install Dependencies
    run: /install.sh

  - name: Build artifacts
    run: /build.sh

  - uses: WarpBuilds/cache/save@v1
    id: cache
    with:
      path: path/to/dependencies
      key: ${{ runner.os }}-${{ hashFiles('**/lockfiles') }}

With this save action, the key can now be re-evaluated while executing the action. This helps in cases where lockfiles are generated during the build.

Let's say we have a restore step that computes a key at runtime.

uses: WarpBuilds/cache/restore@v1
id: restore-cache
with:
    key: cache-${{ hashFiles('**/lockfiles') }}

uses: WarpBuilds/cache/save@v1
with:
    key: ${{ steps.restore-cache.outputs.cache-primary-key }}

uses: WarpBuilds/cache/save@v1
with:
    key: npm-cache-${{hashfiles(package-lock.json)}}

There are instances where some flaky test cases would fail the entire workflow and users would get frustrated because the builds would run for hours and the cache couldn't be saved as the workflow failed in between. For such use-cases, users now have the ability to use the WarpBuilds/cache/save action to save the cache by using an if: always() condition. This way the cache will always be saved if generated, or a warning will be generated that nothing is found on the cache path. Users can also use the if condition to only execute the WarpBuilds/cache/save action depending on the output of previous steps. This way they get more control of when to save the cache.

steps:
  - uses: actions/checkout@v3
  .
  . // restore if need be
  .
  - name: Build
    run: /build.sh
  - uses: WarpBuilds/cache/save@v1
    if: always() // or any other condition to invoke the save action
    with:
      path: path/to/dependencies
      key: ${{ runner.os }}-${{ hashFiles('**/lockfiles') }}