setup-node can't use zstd compression in Ubuntu 22.04 runners

[bateleurX]

Description:
setup-node can't manipulate zstd cache archives in Ubuntu 22.04 runners.
actions/cache ver 3.0.4 that is used by setup-node has a bug(actions/toolkit#1353) that blocks zstd usage on Ubuntu 22.04 runners.

Update dependent npm package actions/cache to versions >=3.1.4 to use zstd archive in Ubuntu 22.04 runners.

Action version:
v3.7.0

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:
pnpm 8.6.0

Repro steps:
Create pnpm cache with following workflow

runs:
  steps:
    - uses: pnpm/action-setup@v2
    - uses: actions/setup-node@v3
      with:
        node-version-file: '.node-version'
        cache: pnpm
    - run: pnpm install --frozen-lockfile
      shell: bash

Expected behavior:
Cache archive should be compressed in zstd.

Actual behavior:
Cache archive is compressed in gzip.

Post job cleanup.
Post job cleanup.
/usr/bin/tar --posix -z -cf cache.tgz --exclude cache.tgz -P -C /home/runner/work/abcde/abcde --files-from manifest.txt
Cache Size: ~208 MB (217621075 B)
Cache saved successfully
Cache saved with the key: node-cache-Linux-pnpm-1234567890abcdef
Post job cleanup.
Pruning is unnecessary.

[dusan-trickovic]

Hello, @bateleurX ! Thank you for reporting this issue, we will investigate it and see what can be done :)

[dmitry-shibanov]

Hello @bateleurX. We've merged the pull request with updating toolkit/cache to the latest version. Could you please try to use actions/setup-node@main to confirm that it works as expected ?

[bateleurX]

Hello @dmitry-shibanov
I tried using actions/setup-node@main and noticed that zstd is used. Thank you for your correspondence!

Post job cleanup.
Post job cleanup.
/usr/bin/tar --posix -cf cache.tzst --exclude cache.tzst -P -C /home/runner/work/abcde/abcde --files-from manifest.txt --use-compress-program zstdmt
Cache Size: ~209 MB (218734115 B)
Cache saved successfully
Cache saved with the key: node-cache-Linux-pnpm-1234567890abcdef
Post job cleanup.
Pruning is unnecessary.

[dmitry-shibanov]

Thank you for your response @bateleurX. I will keep the issue opened until the new version of setup-node is released.

[dmitry-shibanov]

Hello @bateleurX. The new version of setup-node was released. For now I'm going to close the issue. If you have any concerns feel free to ping us.