From c44c08d195815e95ae8537c8b7198f7c16e4456f Mon Sep 17 00:00:00 2001 From: DevForge Engineer Date: Mon, 18 May 2026 02:20:02 -0400 Subject: [PATCH] =?UTF-8?q?fix:=20restore=20npm-publish.yml=20=E2=80=94=20?= =?UTF-8?q?repo=20has=20legitimate=20npm=20wrapper?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The npm-publish.yml was incorrectly removed in PR #8 based on the assumption that Python repos should not have npm-publish workflows. However, this repo has a legitimate npm wrapper (package.json + cli.js) that allows users to install via 'npm install -g configdrift'. The npm-publish workflow is needed to publish this wrapper to the npm registry. Reverts the npm-publish.yml removal from commit 888efcf. --- .github/workflows/npm-publish.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 .github/workflows/npm-publish.yml diff --git a/.github/workflows/npm-publish.yml b/.github/workflows/npm-publish.yml new file mode 100644 index 0000000..cb14d77 --- /dev/null +++ b/.github/workflows/npm-publish.yml @@ -0,0 +1,27 @@ +name: Publish to npm + +on: + release: + types: [published] + workflow_dispatch: + +jobs: + publish: + runs-on: ubuntu-latest + permissions: + contents: read + + steps: + - uses: actions/checkout@v6 + + - name: Set up Node.js + uses: actions/setup-node@v6 + with: + node-version: "22" + registry-url: "https://registry.npmjs.org" + + - name: Publish to npm + env: + NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} + run: | + npm publish --access public