Josh Soref
Josh Soref
@JJ: Assuming that the runtime is performing hashFiles() at step evaluation, you should be able to perform your own hashing on disk in a step... Old: ```yaml - name: Cache...
There were only [27 commits](https://github.com/actions/upload-artifact/compare/v3...v4.0.0) according to the [v4.0.0 release notes](https://github.com/actions/upload-artifact/releases/tag/v4.0.0). Breaking changes (and this definitely is a breaking change) should absolutely be called out in major version bump releases'...
@robherley > Uploads and downloads must use the same actions versions. It isn't _obvious_ that you mean "the same _major_ action version." -- If that's what's intended.
@robherley in https://github.com/actions/upload-artifact/issues/478#issuecomment-1885470013 you pointed to: https://github.com/actions/download-artifact/blob/main/docs/MIGRATION.md I believe I've made a faithful reproduction of your workflow (v3 and v4), and it is *not* a drop-in replacement. https://github.com/check-spelling-sandbox/artifact-merge-hell/actions/runs/7729203589/job/21071843037 ```diff -Run...
Thanks, with that change, the results now do look compatible: https://github.com/check-spelling-sandbox/artifact-merge-hell/actions/runs/7730117258
Not actively. I started this project a while ago. This change isn't essential especially for an end of life plug-in. The other change to fix how the warning presents itself...
I'd encourage you to move those items out of the main `README.md` as its contents are displayed in the npmjs view...