@clipwright/mcp-server 0.18.0 → 0.19.0
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/CHANGELOG.md +30 -0
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -16,6 +16,36 @@ a customer reading it should not miss what appeared in the product. Like *Server
|
|
|
16
16
|
they are live from the day the web app was deployed, not from the package release they are
|
|
17
17
|
listed under.
|
|
18
18
|
|
|
19
|
+
## [0.19.0] - 2026-09-22
|
|
20
|
+
|
|
21
|
+
A paid video that arrived after we stopped waiting can now be collected: the run
|
|
22
|
+
goes back to `queued` and drives the pipeline again. The server side was live
|
|
23
|
+
from the day it was deployed; this release carries the contract change to the
|
|
24
|
+
MCP tool description, which is where an agent reads the promise.
|
|
25
|
+
|
|
26
|
+
### Changed
|
|
27
|
+
|
|
28
|
+
- **Breaking:** `failed` is no longer always final. A run whose paid vendor job
|
|
29
|
+
we still hold can be reopened: it goes back to `queued` and may reach
|
|
30
|
+
`succeeded`. Every reopening is named in `warnings[]`, and one run is reopened
|
|
31
|
+
at most three times. An agent that stops polling the moment it reads `failed`
|
|
32
|
+
will miss a video that was paid for and delivered.
|
|
33
|
+
- *Server-side* A run that lost the video while the vendor was still working on
|
|
34
|
+
it no longer says its paid job "was retained for recovery" when this run's
|
|
35
|
+
terms cannot support recovery. Reading the terms fails soft: when they cannot
|
|
36
|
+
be read at all, the run promises nothing either way.
|
|
37
|
+
- *Server-side* A recovered delivery is written to the ledger under its own
|
|
38
|
+
reason, `run_recovered_delivery`, because the vendor spend was already counted
|
|
39
|
+
on the day the run first failed.
|
|
40
|
+
|
|
41
|
+
### Operations
|
|
42
|
+
|
|
43
|
+
- Migration 0036 adds `recovery_attempt` and `recovery_reopened_at` to `runs`,
|
|
44
|
+
and both are read on the main render path. **Apply the migration before
|
|
45
|
+
deploying any service**: an early deploy fails every `make_ugc` run, not one
|
|
46
|
+
feature. Order forward is migration, api, worker, web; backwards it is worker
|
|
47
|
+
and api first, then drop the columns.
|
|
48
|
+
|
|
19
49
|
## [0.18.0] - 2026-09-21
|
|
20
50
|
|
|
21
51
|
Long-form clips can now show a face for a fifth of their length instead of nearly
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@clipwright/mcp-server",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.19.0",
|
|
4
4
|
"description": "MCP server for Clipwright: generate UGC videos from your coding agent",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"mcp",
|
|
@@ -29,8 +29,8 @@
|
|
|
29
29
|
"dependencies": {
|
|
30
30
|
"@modelcontextprotocol/sdk": "^1.29.0",
|
|
31
31
|
"zod": "^4.4.3",
|
|
32
|
-
"@clipwright/core": "0.
|
|
33
|
-
"@clipwright/sdk": "0.
|
|
32
|
+
"@clipwright/core": "0.19.0",
|
|
33
|
+
"@clipwright/sdk": "0.19.0"
|
|
34
34
|
},
|
|
35
35
|
"devDependencies": {
|
|
36
36
|
"@types/node": "^26.1.1"
|