@minnovate/shadow-publisher 0.17.0 → 0.17.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.17.
|
|
4
|
+
"version": "0.17.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"]
|
|
@@ -28,7 +28,7 @@ Every command accepts `--json` and prints exactly one JSON object on stdout. Exi
|
|
|
28
28
|
publisher --version
|
|
29
29
|
```
|
|
30
30
|
|
|
31
|
-
If the command is not found, or the version is older than 0.
|
|
31
|
+
If the command is not found, or the version is older than 0.16.0, install it:
|
|
32
32
|
`npm install -g @minnovate/shadow-publisher@latest` (it needs Node.js 22.12 or a later 22). In a Claude Cowork task
|
|
33
33
|
this is normal: the sandbox starts empty every time, so install it without asking. On the person's
|
|
34
34
|
own computer, say in one line that you are installing the publisher. If `npm` itself is missing,
|
|
@@ -77,8 +77,9 @@ publisher login --no-wait --json
|
|
|
77
77
|
It prints one JSON object with `userCode` and `verificationUri`, and `next.command`. Then:
|
|
78
78
|
|
|
79
79
|
1. **If a tool named `approve_publisher_sign_in` is available** (the Shadow connector, which the
|
|
80
|
-
person connected in Claude's settings), call it with `userCode`.
|
|
81
|
-
|
|
80
|
+
person connected in Claude's settings), call it with `userCode`. It approves nothing: it answers
|
|
81
|
+
a link with the code in it. Give the person that link, and ask them to check the code and
|
|
82
|
+
approve the sign-in there.
|
|
82
83
|
2. Otherwise give the person `verificationUri` as a link they can click, and `userCode`, and say
|
|
83
84
|
the page will ask them to sign in with their work account.
|
|
84
85
|
3. Run `next.command` — it is `publisher login --continue --json`. It returns `ok: true` within
|