@love-moon/conductor-sdk 0.7.1 → 0.7.2

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @love-moon/conductor-sdk
 
+## 0.7.2
+
+### Patch Changes
+
+- 80c5255: Canonicalize every GitHub SSH host alias (`github.com`, `github-*`,
+  `github.com-*`) to `github.com` when normalizing git remote URLs. GitHub
+  identifies a repository solely by its `owner/repo` path, so the same repo cloned
+  through different SSH aliases (e.g. `github-dang217` vs `github-duinodu`) now
+  merges across daemons by owner/repo instead of being blocked by a hardcoded
+  per-alias allowlist. Non-GitHub hosts (gitlab.com, self-hosted, GitHub
+  Enterprise) are left untouched so unrelated repos never merge.
+
 ## 0.7.1
 
 ### Patch Changes

package/dist/context/project_context.js

@@ -198,8 +198,14 @@ export function normalizeGitRemoteUrl(raw) {
 }
 function canonicalGitRemoteHost(host) {
     const normalized = host.trim().toLowerCase();
-    // SSH config alias used for GitHub remotes in our deployments.
-    if (normalized === 'github-duinodu') {
+    // Any GitHub SSH config alias points at github.com. Users create these in
+    // `~/.ssh/config` to juggle multiple accounts/keys (e.g. `github-duinodu`,
+    // `github-dang217`, `github.com-work`). GitHub identifies a repository solely
+    // by its `owner/repo` path, so we collapse every alias to `github.com` and
+    // let the path decide equality — instead of maintaining a per-alias allowlist.
+    if (normalized === 'github.com' ||
+        normalized.startsWith('github-') ||
+        normalized.startsWith('github.com-')) {
         return 'github.com';
     }
     return normalized;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@love-moon/conductor-sdk",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/lovemoon-ai/conductor.git"
@@ -33,5 +33,5 @@
     "typescript": "^5.6.3",
     "vitest": "^2.1.4"
   },
-  "gitCommitId": "7e2be9c"
+  "gitCommitId": "04c865c"
 }