@minnovate/shadow-publisher 0.9.1 → 0.9.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "git-publisher",
|
|
3
3
|
"displayName": "Git Publisher",
|
|
4
|
-
"version": "0.9.
|
|
4
|
+
"version": "0.9.2",
|
|
5
5
|
"description": "Publish an app folder's Git history to the serverless Git publishing backend and keep it updated (\"publish my app\", \"update my app\", \"fetch the engineered version\").",
|
|
6
6
|
"author": { "name": "git-publisher project" },
|
|
7
7
|
"keywords": ["git", "publish", "deploy", "serverless"]
|
|
@@ -63,6 +63,12 @@ Then read the log every few seconds until it holds a JSON object (`ok: true`), f
|
|
|
63
63
|
In a Claude Cowork task this happens again in every new task, because the sandbox forgets the
|
|
64
64
|
sign-in when the task ends.
|
|
65
65
|
|
|
66
|
+
**If a tool named `approve_publisher_sign_in` is available** (the Shadow publisher connector, which
|
|
67
|
+
the person connected in Claude's settings), do not give them the link: call that tool with the code
|
|
68
|
+
from the log, then keep reading the log as above — it reaches `ok: true` within a few seconds, with
|
|
69
|
+
nothing for the person to do. If the tool answers that it did not approve, give them the link and
|
|
70
|
+
code as above. The tool never returns a credential, and you never need one.
|
|
71
|
+
|
|
66
72
|
**Never ask the user for a token, an endpoint, a URL or a credential — in any words.** They are
|
|
67
73
|
publishing an app; they do not know what those are, and you do not need them: `login` discovers
|
|
68
74
|
where publishing lives and signs them in through their browser. `next.ask` is `null` whenever
|