fix(publish): don’t force npmjs registry via publishConfig

Remove publishConfig.registry so publishing can target other registries
(e.g. GitHub Packages) without npm redirecting back to npmjs.

Also narrow .npmrc scope override to @taskade/eslint-plugin only.

Author: lxcid

.changeset/publishconfig-registry.md

@@ -0,0 +1,5 @@
+---
+"@taskade/temporal-parser": patch
+---
+
+build(ci): Allow publishing to GitHub Packages by removing the hard-coded npmjs registry from `publishConfig`.

.github/workflows/publish.yml

@@ -10,6 +10,7 @@ jobs:
     name: Release
     runs-on: ubuntu-latest
     permissions:
+      id-token: write
       contents: write
       packages: write
       pull-requests: write
@@ -49,9 +50,6 @@ jobs:
           publish: npm run release
           title: 'chore: version packages'
           commit: 'chore: version packages'
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
       # Only publish to GitHub Packages if npm publish succeeded
       - name: Setup Node.js for GitHub Packages

.npmrc

@@ -1,2 +1,2 @@
-# Override global @taskade scope to use public npm registry for this project
-@taskade:registry=https://registry.npmjs.org/
+# Use public npm registry for @taskade/eslint-plugin only
+@taskade/eslint-plugin:registry=https://registry.npmjs.org/

package.json

@@ -28,8 +28,7 @@
     "url": "git+https://github.com/taskade/temporal-parser.git"
   },
   "publishConfig": {
-    "access": "public",
-    "registry": "https://registry.npmjs.org"
+    "access": "public"
   },
   "keywords": [
     "temporal",