From d84858ee6c4c52170550ec37c3776252f9f40bf9 Mon Sep 17 00:00:00 2001
From: Thomas Heartman <thomas@getunleash.ai>
Date: Thu, 9 Jan 2025 13:16:44 +0100
Subject: [PATCH] chore: accept unleash bot secrets in npm workflow (#31)

Because the secrets need to be passed from the calling workflow, we
need to specify them as incoming secrets (otherwise the calling
workflow will fail).
---
 .github/workflows/npm-release.yml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/.github/workflows/npm-release.yml b/.github/workflows/npm-release.yml
index 2906b23..a6ddef1 100644
--- a/.github/workflows/npm-release.yml
+++ b/.github/workflows/npm-release.yml
@@ -20,6 +20,12 @@ on:
         type: string
         default: "yarn install --frozen-lockfile"
     secrets:
+      UNLEASH_BOT_APP_ID:
+        description: "The app ID for the Unleash bot"
+        required: true
+      UNLEASH_BOT_PRIVATE_KEY:
+        description: "The private key for the Unleash bot"
+        required: true
       NPM_ACCESS_TOKEN:
         description: "NPM token allowed to push to the registry"
         required: true