fix: extend existing environment when invoking syft instead of creati…

…ng a new one (#455) Signed-off-by: Noah Krause <krausenoah@gmail.com>
anchore · Mar 27, 2024 · 04a486a · 04a486a
1 parent ab5d7b5
commit 04a486a
Show file tree

Hide file tree

Showing 5 changed files with 8 additions and 9 deletions.
diff --git a/DEVELOPING.md b/DEVELOPING.md
@@ -8,6 +8,10 @@ If you would like to get more extensive debug logging, it is
 possible to enable this as [described here](https://github.com/actions/toolkit/blob/master/docs/action-debugging.md)
 by setting a secret in your repository of `ACTIONS_STEP_DEBUG` to `true`.
 
+## Update `dist/`
+
+Updates to `dist/` and handled via a commit hook. Install the hook by running `npm install`.
+
 ## Tests
 
 To run tests locally, you will need a local docker instance and registry along with a few

diff --git a/dist/attachReleaseAssets/index.js b/dist/attachReleaseAssets/index.js
diff --git a/dist/downloadSyft/index.js b/dist/downloadSyft/index.js
diff --git a/dist/runSyftAction/index.js b/dist/runSyftAction/index.js
diff --git a/src/github/SyftGithubAction.ts b/src/github/SyftGithubAction.ts
@@ -109,6 +109,7 @@ async function executeSyft({
   const cmd = await getSyftCommand();
 
   const env: { [key: string]: string } = {
+    ...process.env,
     SYFT_CHECK_FOR_APP_UPDATE: "false",
   };