@shipstatic/mcp 1.12.0 → 1.12.2-beta.1

package/dist/vocabulary.d.ts

@@ -95,11 +95,13 @@ export declare const UPLOAD_TOOL_TITLE = "Deploy Static Site";
  * to carry its own unit, and dividing by 86400 at eight sites would restate the
  * unit eight times instead of the number.
  *
- * The unit stays literal, and that is the one assumption here: this reads
- * correctly while the TTL is a whole number of days, which it has always been.
- * A TTL of hours would need the prose reviewed anyway — the widget's own
- * `formatExpires` speaks in days and hours too — so the honest failure is a
- * sentence someone must rewrite, not a number that silently rounds.
+ * Spelled by `formatDuration` since 2026-09-17, the platform's one way of
+ * saying a span of time, so the lifetime an agent is promised and the time a
+ * fresh deployment's card and CLI note say it has left are one spelling. It
+ * was `${TTL / 86_400} days` until then, correct only while the TTL was a
+ * whole number of days: a one-day lifetime would have read "1 days". The
+ * spelling still rounds a lifetime that is not a whole number of its unit
+ * (84 hours reads "4 days"), which no lifetime the platform has had needs.
  */
 export declare const PUBLIC_EXPIRY: string;
 /**

package/dist/vocabulary.js

@@ -29,6 +29,7 @@
  */
 import { IDEMPOTENCY_KEY_CONSTRAINTS, LABEL_CONSTRAINTS, PASSWORD_CONSTRAINTS, } from '@shipstatic/ship';
 import { PUBLIC_DEPLOYMENT_TTL_SECONDS } from '@shipstatic/types';
+import { formatDuration } from '@shipstatic/types/time';
 /**
  * Two packages, and the split is a rule rather than an accident: **read a
  * constant from whatever will act on it.**
@@ -97,13 +98,15 @@ export const UPLOAD_TOOL_TITLE = 'Deploy Static Site';
  * to carry its own unit, and dividing by 86400 at eight sites would restate the
  * unit eight times instead of the number.
  *
- * The unit stays literal, and that is the one assumption here: this reads
- * correctly while the TTL is a whole number of days, which it has always been.
- * A TTL of hours would need the prose reviewed anyway — the widget's own
- * `formatExpires` speaks in days and hours too — so the honest failure is a
- * sentence someone must rewrite, not a number that silently rounds.
+ * Spelled by `formatDuration` since 2026-09-17, the platform's one way of
+ * saying a span of time, so the lifetime an agent is promised and the time a
+ * fresh deployment's card and CLI note say it has left are one spelling. It
+ * was `${TTL / 86_400} days` until then, correct only while the TTL was a
+ * whole number of days: a one-day lifetime would have read "1 days". The
+ * spelling still rounds a lifetime that is not a whole number of its unit
+ * (84 hours reads "4 days"), which no lifetime the platform has had needs.
  */
-export const PUBLIC_EXPIRY = `${PUBLIC_DEPLOYMENT_TTL_SECONDS / 86_400} days`;
+export const PUBLIC_EXPIRY = formatDuration(PUBLIC_DEPLOYMENT_TTL_SECONDS);
 /**
  * The MCP annotations a tool's contract implies. An agent reads them to
  * decide whether it may call speculatively (`readOnlyHint`), whether it must

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shipstatic/mcp",
-  "version": "1.12.0",
+  "version": "1.12.2-beta.1",
   "mcpName": "com.shipstatic/mcp",
   "description": "Deploy static websites, landing pages, and prototypes instantly from AI agents. Start with the hosted endpoint at mcp.shipstatic.com (no install, no signup, no API key), or install this package to deploy folders from your own machine. The same fifteen tools either way.",
   "type": "module",
@@ -68,8 +68,8 @@
   "license": "MIT",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.30.0",
-    "@shipstatic/ship": "2.9.2",
-    "@shipstatic/types": "2.25.0",
+    "@shipstatic/ship": "2.9.4-beta.1",
+    "@shipstatic/types": "2.26.0-beta.1",
     "zod": "^4.4.3"
   },
   "devDependencies": {