build(ci): explicitly set GitHub Packages registry in publish step (#3)

The GitHub Packages publish step was incorrectly attempting to publish
to npm registry instead of GitHub Packages. This adds the explicit
--registry flag to ensure it publishes to the correct registry.

Without this flag, the setup-node registry configuration was being
overridden by the prepublishOnly script, causing the publish to target
npm instead of GitHub Packages.

Author: lxcid

.changeset/long-drinks-grin.md

@@ -0,0 +1,5 @@
+---
+"@taskade/temporal-parser": patch
+---
+
+build(ci): Fix GitHub Packages publish workflow to use correct registry. Previously, the GitHub Packages publish step was attempting to publish to npm registry instead of GitHub Packages registry. This adds the explicit `--registry` flag to ensure packages are published to the correct location.

.github/workflows/publish.yml

@@ -64,6 +64,6 @@ jobs:
 
       - name: Publish to GitHub Packages
         if: steps.changesets.outputs.published == 'true'
-        run: npm publish
+        run: npm publish --registry=https://npm.pkg.github.com
         env:
           NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}