@minnovate/shadow-publisher 0.15.1 → 0.15.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.15.
|
|
4
|
+
"version": "0.15.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"]
|
|
@@ -182,7 +182,10 @@ following, for when the person asks not to wait.
|
|
|
182
182
|
checked, and this organisation does not deploy automatically. `"failed"` with `findings`: it
|
|
183
183
|
did not pass its checks, and `findings` says why — fix them as "When the checks find something"
|
|
184
184
|
below says. `"failed"` without `findings`: it stopped at `failedAt`; the portal says why — do
|
|
185
|
-
not guess the reason.
|
|
185
|
+
not guess the reason. A fault on our side can be tried again: to find out, run `publisher
|
|
186
|
+
question . --json` and follow the `sync-app` skill's section
|
|
187
|
+
"When it did not go live because of a fault on our side".
|
|
188
|
+
`"stopped"`: a newer publication replaced it.
|
|
186
189
|
- `"moving"` or `"timed-out"`: still going; follow it as step 4 says. After about 15 minutes in
|
|
187
190
|
all, stop and point them to the portal (`progress.portal`).
|
|
188
191
|
- `"unauthorized"`: published, but the portal did not accept this sign-in; run `publisher login`
|
|
@@ -44,14 +44,15 @@ again. Then `publisher follow . --publication <id> --until-change --timeout 100
|
|
|
44
44
|
|
|
45
45
|
## When it did not go live because of a fault on our side
|
|
46
46
|
|
|
47
|
-
When `publisher question . --json` shows a `blocked` preparation
|
|
48
|
-
was on our side, not in the app
|
|
47
|
+
When `publisher question . --json` shows a `blocked` preparation with `canRetry: true`, the fault
|
|
48
|
+
was on our side, not in the app (its `message` says so). Do not change the app. Try it again once:
|
|
49
49
|
|
|
50
50
|
```bash
|
|
51
51
|
publisher retry . --json
|
|
52
52
|
```
|
|
53
53
|
|
|
54
|
-
Then follow it again. If it fails a second time, tell the person, and
|
|
54
|
+
Then follow it again. If it fails a second time, or `canRetry` is `false`, tell the person, and
|
|
55
|
+
give them the portal page.
|
|
55
56
|
|
|
56
57
|
## After it is live
|
|
57
58
|
|