ci: publish to npmjs with npm token

Author: omarsdev

.github/workflows/publish.yml

@@ -23,19 +23,17 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: 18
-          registry-url: https://npm.pkg.github.com/
-          scope: '@omarsdev'
+          registry-url: https://registry.npmjs.org/
           cache: 'yarn'
 
-      - name: Write npmrc for GitHub Packages
+      - name: Configure npm auth
         run: |
           cat <<'EOF' > .npmrc
-          @omarsdev:registry=https://npm.pkg.github.com
-          //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
+          //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
           always-auth=true
           EOF
         env:
-          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_PACKAGES_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
       - name: Install dependencies
         run: yarn install --frozen-lockfile
@@ -55,7 +53,7 @@ jobs:
       - name: Publish to GitHub Packages
         run: npm publish
         env:
-          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_PACKAGES_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
       - name: Push version bump
         run: |

README.md

@@ -59,4 +59,4 @@ Merges to `develop` trigger the `Publish Package` GitHub Action, which:
 - publishes the build to GitHub Packages
 - pushes the updated version and tag back to `develop`
 
-Before the workflow can publish, add a repository secret named `GITHUB_PACKAGES_TOKEN` that contains a GitHub personal access token with `write:packages` and `read:packages` scopes (include `delete:packages` if you expect to remove releases). The workflow injects this token into `npm publish` via the `NODE_AUTH_TOKEN` environment variable.
+Before the workflow can publish, add a repository secret named `NPM_TOKEN` that contains an npm automation token (publish scope). The workflow injects this token into `npm publish` via the `NODE_AUTH_TOKEN` environment variable.