From ae26aaf1b56fb80d170677751f3399908c8eb107 Mon Sep 17 00:00:00 2001
From: Maxim Lobanov <v-malob@microsoft.com>
Date: Wed, 26 May 2021 17:27:14 +0300
Subject: [PATCH] Update 0000-caching-dependencies.md
---
docs/adrs/0000-caching-dependencies.md | 1 -
1 file changed, 1 deletion(-)
diff --git a/docs/adrs/0000-caching-dependencies.md b/docs/adrs/0000-caching-dependencies.md
index 16193f71..641bf838 100644
--- a/docs/adrs/0000-caching-dependencies.md
+++ b/docs/adrs/0000-caching-dependencies.md
@@ -26,7 +26,6 @@ We don't persue the goal to provide wide customization of caching in scope of `a
- Add optional input `package-lock-path` that will allow to specify path to `package-lock.json` file path:
- 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
- If input contains file path, action will use the specified file
- - If input contains folder path, action will try to search `package-lock.json` file in the specified folder
- if input contains wildcards (like `**/package-lock.json`), hash of multiple files will be used
- 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)
- The following key cache will be used `${{ runner.os }}-npm-${{ hashFiles('<package-lock-path>') }}`