You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/adrs/0000-caching-dependencies.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,6 @@ We don't persue the goal to provide wide customization of caching in scope of `a
26
26
- Add optional input `package-lock-path` that will allow to specify path to `package-lock.json` file path:
27
27
- If input is not defined, action will try to search `package-lock.json` or `yarn.lock` (npm 7.x supports `yarn.lock` files) files in the repository root and throw error if no one is found
28
28
- If input contains file path, action will use the specified file
29
-
- If input contains folder path, action will try to search `package-lock.json` file in the specified folder
30
29
- if input contains wildcards (like `**/package-lock.json`), hash of multiple files will be used
31
30
- The hash of file provided in `package-lock-path` input will be used as cache key (the same approach like [actions/cache](https://github.com/actions/cache/blob/main/examples.md#node---npm) recommends)
32
31
- The following key cache will be used `${{ runner.os }}-npm-${{ hashFiles('<package-lock-path>') }}`
0 commit comments