From 52a9c5db07b1e3ee5adac09ebaa64a2d05301fad Mon Sep 17 00:00:00 2001
From: Mason Williams <mason@onkernel.com>
Date: Fri, 6 Feb 2026 15:58:52 -0500
Subject: [PATCH] fix: publish to npm registry directly instead of Yarn proxy

Yarn's registry proxy (registry.yarnpkg.com) is failing with "Not found"
for scoped package publishes. Explicitly set the npm registry in
publishConfig to bypass the proxy.

Co-authored-by: Cursor <cursoragent@cursor.com>
---
 package.json | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/package.json b/package.json
index 5b65c05..f101fe4 100644
--- a/package.json
+++ b/package.json
@@ -14,7 +14,8 @@
   ],
   "private": false,
   "publishConfig": {
-    "access": "public"
+    "access": "public",
+    "registry": "https://registry.npmjs.org"
   },
   "scripts": {
     "test": "./scripts/test",