Do you know if bsd tar will be available on all windows versions? Including windows servers?

If we are concerned about tar differences, would it be more safe to use the npm tar package? https://www.npmjs.com/package/tar

Do you know if bsd tar will be available on all windows versions? Including windows servers?

Based on https://docs.microsoft.com/en-us/virtualization/community/team-blog/2017/20171219-tar-and-curl-come-to-windows, it was only added in Build 17063, so older versions of Windows won't have it.
I'm not sure if the Windows server will have it. From speaking with @ericsciple, the various npm packages for tar can sometimes be problematic.

The current behavior is that no self-hosted runners will work with actions/cache since it's expecting a GNU tar prepended to the Path, which is unique to our hosted runner images. This at least allows all self-hosted runners using newer versions of Windows to use this action.

Would it be possible to do a 1.0.4 release with this in it? I am trying to set up self-hosted windows runners for a project, but it always fails to cache anything because of the --force-local option not being available on bsdtar and cache ignores the mingw-w64 tar I have first in PATH. I tried to do uses: actions/cache@master but it did not get the dist folder even though it got everything else.

@1480c1 There will be a release soon with this change. In the meantime, if you fork the repository and run npm run release, you should be able to build and commit the dist folder and use that fork of the action.

Okay, thank you. Don't know much about npm yet so I wasn't sure how to solve the issue on my own.