@hailer/mcp 2.0.0-beta.11 → 2.0.0-beta.12
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.
|
@@ -109,12 +109,24 @@ If a publish reports success but the app still serves the old/localhost version,
|
|
|
109
109
|
<prod-publish>
|
|
110
110
|
## Step 5 — Production Publish (only when the user explicitly asks)
|
|
111
111
|
|
|
112
|
+
**FIRST, decide first-publish vs update by READING `public/manifest.json` — never guess, never fail-first.** The scaffold ships a placeholder `appId` of `65143728d2bd678b13daf289` (the "Magic Apps" demo). That value, or empty/missing, means this app has never been published:
|
|
113
|
+
|
|
114
|
+
| manifest `appId` | This is a… | Command |
|
|
115
|
+
|---|---|---|
|
|
116
|
+
| `65143728d2bd678b13daf289`, `""`, or missing | **FIRST publish** | `--create --app-name "<Name>" --workspace <wsId> --force` (all three required with `--create`) |
|
|
117
|
+
| a real 24-char id you created earlier | **update** | `--force` only |
|
|
118
|
+
|
|
119
|
+
A plain publish against the scaffold's placeholder appId silently uploads to the demo app (wrong) or errors — so on a fresh scaffold, ALWAYS take the `--create` path on the very first publish. Get `<wsId>` from `config.json` (`workspaceId`); derive `<Name>` from the project (e.g. "Upcoming Matches") or ask.
|
|
120
|
+
|
|
112
121
|
```bash
|
|
113
|
-
#
|
|
122
|
+
# FIRST publish (fresh scaffold) — local machine
|
|
114
123
|
npm run publish-production -- --create --app-name "<App Name>" --workspace <workspaceId> --force
|
|
115
124
|
|
|
116
|
-
# Hailer Studio (cluster
|
|
125
|
+
# FIRST publish — Hailer Studio (cluster, cannot reach api.hailer.com)
|
|
117
126
|
npm run publish-production -- --host http://hailer-api:1337 --create --app-name "<App Name>" --workspace <workspaceId> --force
|
|
127
|
+
|
|
128
|
+
# UPDATE (manifest already has a real appId)
|
|
129
|
+
npm run publish-production -- --force
|
|
118
130
|
```
|
|
119
131
|
|
|
120
132
|
**PUBLISH FAILURE PLAYBOOK — exact error → exact action, no improvising:**
|