Jon Jensen

Here's some more context, [this is the change](https://github.com/actions/toolkit/commit/da52b358001d3b152ed736de25091af285233dbc) that introduced the new error. I set up a [simpler repo](https://github.com/jenseng/workflow-test/) w/ debug logging enabled. Here's a [failing install on 1.8.16](https://github.com/jenseng/workflow-test/runs/7097613222?check_suite_focus=true), here's...

(apologies for accidentally temporarily closing, the wrong button had focus and i hit enter 🤦 ) Based on the output it sees like this new error has actually uncovered a...

Some more context, this might only affect yarn. Here you can see [npm install works fine](https://github.com/jenseng/workflow-test/runs/7098102884?check_suite_focus=true), it correctly finds the .npm dir: ``` ##[debug]Search path 'C:\Users\runneradmin\.npm' ##[debug]Matched: C:/Users/runneradmin/.npm ##[debug]Cache Paths:...

Looks like the yarn cache dir is [wrong](https://github.com/jenseng/workflow-test/runs/7098328438?check_suite_focus=true) on Windows (and maybe in other scenarios too)? It's trying to archive `C:\Users\runneradmin\.cache\yarn` but should actually archive `C:\Users\runneradmin\AppData\Local\Yarn\Cache`

I suspect any Linux ones that are failing are likely due to running in different containers with a different yarn setup that what this action is [inferring](https://github.com/bahmutov/npm-install/blob/master/index.js#L166) ... seems like...

Any fix should also take into account yarn v1 vs v2/v3, as the mechanism for getting the cache dir is different (`yarn config get cacheFolder`). In yarn 2/3, note the...

Here's another workaround/fix ... As of [v2.2](https://github.com/actions/setup-node/releases/tag/v2.2.0), `actions/setup-node` provides equivalent `cache` functionality. It seems to handle yarn cache dirs correctly, see verbose output [here](https://github.com/jenseng/workflow-test/actions/runs/2579036196) (cache miss) and [here](https://github.com/jenseng/workflow-test/actions/runs/2579044981) (cache hit)....

Ooof, sorry for the radio silence :( ... I'm not using hairtrigger in any of my projects anymore, so I don't spend a whole lot of time on it these...

Is this still an issue? Seems like a fix may have been merged to rails 6 stable here: https://github.com/rails/rails/commit/3285f3df7bc3a7a978428044b5458f1eed30b1a9

You should be able to define multiple triggers using [trigger groups](https://github.com/jenseng/hair_trigger#trigger-groups) ... e.g. ```ruby trigger.after(:update) do |t| t.all do # every row # some sql end t.of("foo") do # some...