davinci-resolve-mcp 4.8.11 → 4.8.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.
- package/CHANGELOG.md +70 -0
- package/README.md +1 -1
- package/README.zh-CN.md +2 -2
- package/install.py +1 -1
- package/package.json +1 -1
- package/src/granular/common.py +1 -1
- package/src/server.py +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,76 @@
|
|
|
2
2
|
|
|
3
3
|
Release history for the DaVinci Resolve MCP Server. The latest release is summarized in the root README; older entries live here to keep the README focused.
|
|
4
4
|
|
|
5
|
+
## What's New in v4.8.12 — the offline suite no longer writes traces, reports or update state into `logs/`
|
|
6
|
+
|
|
7
|
+
Test-harness fix only. No tool, action, or Resolve behaviour changed.
|
|
8
|
+
|
|
9
|
+
### Fixed
|
|
10
|
+
|
|
11
|
+
- **The offline suite wrote synthetic records into the operator's `logs/`.**
|
|
12
|
+
`logs/execution-traces.jsonl`, `logs/execution-reports/` and
|
|
13
|
+
`logs/update-check.json` are the server's defaults, and `tests/offline_guard.py`
|
|
14
|
+
did not move them the way it already moves the audit log, the operation log and
|
|
15
|
+
the media-analysis preferences. Measured with
|
|
16
|
+
`python -m unittest discover -s tests -t .` from a checkout with an empty `logs/`:
|
|
17
|
+
one run appended 1,865 tool-call records (672 KB) to the trace log, wrote an audit
|
|
18
|
+
report for a synthetic execution, and created `update-check.json`. In a main
|
|
19
|
+
checkout the trace records share a file with the real ones, and that file is
|
|
20
|
+
where `list_recent_executions` sends a reviewer.
|
|
21
|
+
- `offline_guard` now points `RESOLVE_MCP_TRACE_FILE`,
|
|
22
|
+
`RESOLVE_MCP_TRACE_REPORT_DIR` and `DAVINCI_RESOLVE_MCP_UPDATE_STATE` at a temp
|
|
23
|
+
directory for the run, unless the caller already set them, and restores them on
|
|
24
|
+
`uninstall`. It sets environment variables instead of swapping functions: the
|
|
25
|
+
server already reads these variables, `src.server` binds its own
|
|
26
|
+
`update_state_path`, and a child process inherits the environment.
|
|
27
|
+
- `tests/test_execution_trace.py` unset two of these variables with a bare
|
|
28
|
+
`os.environ.pop`, which would have removed the redirect for every later test.
|
|
29
|
+
Both classes now scope the change with `mock.patch.dict`.
|
|
30
|
+
- New tripwire `tests/test_repo_logs_isolation.py`. It fails if any of the three
|
|
31
|
+
variables is unset or points into the repo's `logs/`, if the server resolves a
|
|
32
|
+
path other than the one the guard set, or if a traced tool call and its exported
|
|
33
|
+
report reach the real `logs/`. It looks for a unique execution id, so a live
|
|
34
|
+
server appending to the same log cannot make it pass or fail.
|
|
35
|
+
|
|
36
|
+
### Validation
|
|
37
|
+
|
|
38
|
+
- Full offline suite from an empty `logs/`, before and after the change: 1,865 trace
|
|
39
|
+
lines, one report and `update-check.json` before; only `.gitkeep` after. 3,741
|
|
40
|
+
tests run (3 new), 84 skipped, 12 errors, the same 12 as before the change:
|
|
41
|
+
`numpy` and `requests` absent from the venv, `jszip` not installed, and one launch
|
|
42
|
+
attempt stopped by the verification tripwire described below.
|
|
43
|
+
- The new tripwire against the previous guard: 4 failures. With the previous
|
|
44
|
+
`test_execution_trace.py` run first in the same process, it fails on the two
|
|
45
|
+
variables that file popped.
|
|
46
|
+
- Both runs used a `sitecustomize` tripwire that stood in for `DaVinciResolveScript`
|
|
47
|
+
and blocked Resolve launches and outbound requests. It recorded 1,174
|
|
48
|
+
`scriptapp("Resolve")` calls and one `open DaVinci Resolve.app` from the granular
|
|
49
|
+
server, before and after this change.
|
|
50
|
+
[#255](https://github.com/samuelgursky/davinci-resolve-mcp/pull/255) closes that
|
|
51
|
+
gap; it is unrelated to this one. It also recorded one request to GitHub's
|
|
52
|
+
`releases/latest` endpoint, made by `test_scripting_lib_discovery` running
|
|
53
|
+
`install.py`'s update check. The state that check writes is now redirected. The
|
|
54
|
+
request itself is refused by
|
|
55
|
+
[#259](https://github.com/samuelgursky/davinci-resolve-mcp/pull/259).
|
|
56
|
+
- That tripwire missed one child process. `install.verify_resolve_connection`
|
|
57
|
+
replaces `PYTHONPATH` with Resolve's `Modules` directory, so its probe child never
|
|
58
|
+
loaded the tripwire. In both runs `test_the_live_probe_agrees_with_the_summary`
|
|
59
|
+
passed instead of skipping. That child therefore loaded the real scripting module
|
|
60
|
+
and called `scriptapp("Resolve")` against the Resolve that was open, one
|
|
61
|
+
read-only probe per run. This change does not touch that path;
|
|
62
|
+
[#260](https://github.com/samuelgursky/davinci-resolve-mcp/pull/260) puts the test
|
|
63
|
+
behind `RESOLVE_VERIFY=1`.
|
|
64
|
+
- Re-run for this release behind a tripwire that also refuses any child whose
|
|
65
|
+
command line imports the scripting module: 3,741 tests, 85 skipped, 14 errors.
|
|
66
|
+
The extra skip is that probe test. The two extra errors are the `test_doctor_paths`
|
|
67
|
+
probe children the stricter tripwire refuses. The error set matches v4.8.4 under
|
|
68
|
+
the same tripwire, and `logs/` held only `.gitkeep` afterwards.
|
|
69
|
+
- Not run under pytest, which is not installed here. `tests/conftest.py` calls the
|
|
70
|
+
same idempotent `install()`/`uninstall()`. That lifecycle was checked directly:
|
|
71
|
+
a second install is a no-op, uninstall restores the environment, and a value the
|
|
72
|
+
caller set is left alone.
|
|
73
|
+
- No Resolve behaviour changed; live test not required.
|
|
74
|
+
|
|
5
75
|
## What's New in v4.8.11 — the installer's live probe no longer runs in the offline suite
|
|
6
76
|
|
|
7
77
|
Test-only. No tool, action or runtime code changed.
|
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
English | [简体中文](README.zh-CN.md)
|
|
4
4
|
|
|
5
|
-
[](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
|
|
6
6
|
[](https://www.npmjs.com/package/davinci-resolve-mcp)
|
|
7
7
|
[](docs/reference/api-coverage.md)
|
|
8
8
|
[-blue.svg)](#server-modes)
|
package/README.zh-CN.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[English](README.md) | 简体中文
|
|
4
4
|
|
|
5
|
-
[](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
|
|
6
6
|
[](https://www.npmjs.com/package/davinci-resolve-mcp)
|
|
7
7
|
[](docs/reference/api-coverage.md)
|
|
8
8
|
[-blue.svg)](#服务器模式)
|
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
[](https://www.python.org/downloads/)
|
|
13
13
|
[](https://opensource.org/licenses/MIT)
|
|
14
14
|
|
|
15
|
-
> 本翻译对应 v4.8.
|
|
15
|
+
> 本翻译对应 v4.8.12 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
|
|
16
16
|
|
|
17
17
|
一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
|
|
18
18
|
|
package/install.py
CHANGED
|
@@ -37,7 +37,7 @@ from src.utils.update_check import (
|
|
|
37
37
|
|
|
38
38
|
# ─── Version ──────────────────────────────────────────────────────────────────
|
|
39
39
|
|
|
40
|
-
VERSION = "4.8.
|
|
40
|
+
VERSION = "4.8.12"
|
|
41
41
|
# Only hard floor: mcp[cli] requires Python 3.10+. There is no upper bound —
|
|
42
42
|
# Resolve's scripting bridge loads into newer interpreters on recent builds
|
|
43
43
|
# (Python 3.14 verified against Resolve Studio 20.3.2). Older Resolve builds
|
package/package.json
CHANGED
package/src/granular/common.py
CHANGED
|
@@ -93,7 +93,7 @@ if not logging.getLogger().handlers:
|
|
|
93
93
|
handlers=[logging.StreamHandler()],
|
|
94
94
|
)
|
|
95
95
|
|
|
96
|
-
VERSION = "4.8.
|
|
96
|
+
VERSION = "4.8.12"
|
|
97
97
|
logger = logging.getLogger("davinci-resolve-mcp")
|
|
98
98
|
logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
|
|
99
99
|
logger.info(f"Detected platform: {get_platform()}")
|