From 323242712c942715a039cc3785b0d9cbc87d153c Mon Sep 17 00:00:00 2001 From: James Newman Date: Fri, 12 Jun 2026 11:40:47 -0400 Subject: [PATCH] =?UTF-8?q?fix(release):=20unblock=20npm=20publish=20?= =?UTF-8?q?=E2=80=94=20remove=20broken=20kit=20install,=20add=20payment=20?= =?UTF-8?q?ext?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Release NPM workflow ran `npm ci` in Kits/Rokt, which requires a package-lock.json. The kits are dependency-less and carry no lock file, so `npm ci` failed with EUSAGE and the 4.0.0 release published the plugin but not the Rokt kit, and created no tag or GitHub release. The kits have no dependencies and no lifecycle scripts, so `npm publish` packs and uploads on its own — no install step is needed. Remove the Rokt kit install step entirely (rather than swapping `npm ci` for `npm install`), and add the missing RoktPaymentExtension publish step (new in 4.0.0, with publishConfig, but never published because the workflow had no step for it). Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/release-from-main.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/release-from-main.yml b/.github/workflows/release-from-main.yml index c4815fb..fe8538c 100644 --- a/.github/workflows/release-from-main.yml +++ b/.github/workflows/release-from-main.yml @@ -52,14 +52,14 @@ jobs: working-directory: plugin run: npm publish --access public - - name: Install Rokt Kit dependencies - working-directory: Kits/Rokt - run: npm ci - - name: Publish Rokt Kit to npm working-directory: Kits/Rokt run: npm publish --access public + - name: Publish Rokt Payment Extension to npm + working-directory: Kits/RoktPaymentExtension + run: npm publish --access public + - uses: ffurrer2/extract-release-notes@273da39a24fb7db106a35526c8162815faffd31d # v3.1.0 id: extract-release-notes with: