@tupaas/mcp 1.3.0 → 1.3.1
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.
- package/dist/index.js +2 -2
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -6,7 +6,7 @@ import fs from "fs";
|
|
|
6
6
|
import path from "path";
|
|
7
7
|
import os from "os";
|
|
8
8
|
import { execSync } from "child_process";
|
|
9
|
-
const VERSION = "1.3.
|
|
9
|
+
const VERSION = "1.3.1";
|
|
10
10
|
const API_URL = process.env.TUPAAS_API_URL ?? "https://tupaas.dev/api";
|
|
11
11
|
const API_KEY = process.env.TUPAAS_API_KEY ?? "";
|
|
12
12
|
const CONFIG_FILE = ".tupaas.json";
|
|
@@ -302,7 +302,7 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
|
|
|
302
302
|
content: [
|
|
303
303
|
{
|
|
304
304
|
type: "text",
|
|
305
|
-
text: `Deploy
|
|
305
|
+
text: `Deploy FAILED\n\nDeploy ID: ${result.deployId}\nProject: ${result.projectSlug}\nStatus: ${finalStatus}\n\n--- Logs ---\n${lastLogs || "No logs available"}\n--- End Logs ---\n\nAnalyze the logs above to identify the error. Common causes: missing environment variables, wrong start command, port mismatch, or missing dependencies. Fix the issue in the source code and redeploy.`,
|
|
306
306
|
},
|
|
307
307
|
],
|
|
308
308
|
};
|