From ad699899c906a381b690d58bbe041850b1b7da1d Mon Sep 17 00:00:00 2001 From: jdalton Date: Tue, 28 Jul 2026 19:44:40 -0400 Subject: [PATCH] fix(ci): use fleet setup-and-install instead of npm ci in publish workflow The publish workflow ran npm ci, but this repo is pnpm-locked (only pnpm-lock.yaml exists, and devEngines pins pnpm with onFail=error), so the install step fails before any store publish can happen. Replace the setup-node + npm ci pair with the local fleet setup-and-install composite, invoked exactly as ci.yml invokes it. --- .github/workflows/publish.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index d0e6ef70..a7e6f94d 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -28,8 +28,9 @@ jobs: - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2 (2026-05-15) with: persist-credentials: false - - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0 (2026-05-15) - - run: npm ci + - uses: ./.github/actions/fleet/setup-and-install + with: + socket-api-token: ${{ secrets.SOCKET_API_TOKEN_FOR_CLI_AND_SFW }} - name: Publish to Open VSX Registry if: success() || failure() uses: ./.github/actions/repo/publish-vscode-extension