davinci-resolve-mcp 4.8.9 → 4.8.11
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 +100 -0
- package/README.md +1 -1
- package/README.zh-CN.md +2 -2
- package/docs/process/release-process.md +8 -0
- 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,106 @@
|
|
|
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.11 — the installer's live probe no longer runs in the offline suite
|
|
6
|
+
|
|
7
|
+
Test-only. No tool, action or runtime code changed.
|
|
8
|
+
|
|
9
|
+
### Fixed
|
|
10
|
+
|
|
11
|
+
- **Every run of the offline suite connected to an open Resolve through the
|
|
12
|
+
installer probe.** `test_scripting_lib_discovery.test_the_live_probe_agrees_with_the_summary`
|
|
13
|
+
runs the real `install.verify_resolve_connection` whenever Resolve is
|
|
14
|
+
installed. The probe's child sets PYTHONPATH to Blackmagic's Modules
|
|
15
|
+
directory. So neither the offline guard's child site from v4.8.9 nor a
|
|
16
|
+
PYTHONPATH tripwire loads in it, and it imports the real module and calls
|
|
17
|
+
`scriptapp("Resolve")`, `GetProductName` and `GetVersionString`. v4.8.9 named
|
|
18
|
+
this path and left it open. In the four full runs behind v4.8.9, with Resolve
|
|
19
|
+
open, the test passed rather than skipped. It skips when the probe does not
|
|
20
|
+
answer, so each of those runs called `scriptapp("Resolve")` on the real module
|
|
21
|
+
(read-only).
|
|
22
|
+
- The test now runs only with `RESOLVE_VERIFY=1`, the switch the live harnesses
|
|
23
|
+
already use. The check happens when the test runs, not in a decorator at
|
|
24
|
+
import, so it can be tested. The installed-Resolve check still applies after
|
|
25
|
+
it.
|
|
26
|
+
- `docs/process/release-process.md` now names the command, for changes to the
|
|
27
|
+
installer's verification or summary.
|
|
28
|
+
|
|
29
|
+
### Validation
|
|
30
|
+
|
|
31
|
+
- New `test_the_live_test_runs_only_when_asked` runs the live test with the host
|
|
32
|
+
made to look installed, discovery pinned and the probe booby-trapped. With
|
|
33
|
+
`RESOLVE_VERIFY=1` the trap goes off once, which shows it is armed. Without it
|
|
34
|
+
the test skips, naming the switch, and never reaches the trap. With the opt-in
|
|
35
|
+
check removed, the new test fails.
|
|
36
|
+
- Full suite, `python -m unittest discover -s tests -t .` and
|
|
37
|
+
`python -m unittest discover -s tests`: 3,771 tests each, 85 skipped. On v4.8.9
|
|
38
|
+
it was 84 of 3,770, and the one new skip is the live test. The 11 errors are the
|
|
39
|
+
same as on v4.8.8 in this environment (no `numpy` or `requests` in the venv, plus
|
|
40
|
+
`test_offline_fallback` and `test_lut_file_controls`).
|
|
41
|
+
- The tripwire used for validation now also refuses a child that names
|
|
42
|
+
Blackmagic's module and points at the real install on its command line or
|
|
43
|
+
PYTHONPATH. That is the shape of the installer and doctor probes. It recorded no
|
|
44
|
+
`scriptapp` call, native load, launch or refused probe child in either run.
|
|
45
|
+
- No Resolve behavior changed, so no live Resolve run is required. None was made.
|
|
46
|
+
|
|
47
|
+
## What's New in v4.8.10 — the offline suite no longer asks GitHub for the latest release
|
|
48
|
+
|
|
49
|
+
No tool, action or runtime behaviour changed. This release changes the test
|
|
50
|
+
harness only.
|
|
51
|
+
|
|
52
|
+
### Fixed
|
|
53
|
+
|
|
54
|
+
- **Every full offline run sent a live request to GitHub.** `install.py` checks
|
|
55
|
+
`https://api.github.com/repos/samuelgursky/davinci-resolve-mcp/releases/latest`
|
|
56
|
+
for a newer version, and `tests/test_scripting_lib_discovery.py` runs its
|
|
57
|
+
`main()` in-process (`install.py --clients manual --dry-run`) through
|
|
58
|
+
`_run_main`. So `python -m unittest discover -s tests -t .` made that request
|
|
59
|
+
on every run. The run's outcome depended on the machine being online, and the
|
|
60
|
+
release notes that came back were written into `logs/update-check.json`.
|
|
61
|
+
Redirecting that file moves the answer, not the request. Measured on a full
|
|
62
|
+
v4.8.4 run with a tripwire wrapped around `urllib.request.urlopen`: exactly one
|
|
63
|
+
outbound request, this one, from
|
|
64
|
+
`test_only_the_designated_live_test_touches_a_real_resolve` →
|
|
65
|
+
`test_a_failed_verification_exits_non_zero` → `_run_main` →
|
|
66
|
+
`update_check.check_for_updates` → `_fetch_latest_release`. The same run of
|
|
67
|
+
this release makes none.
|
|
68
|
+
- `tests/offline_guard.py` now also wraps `urllib.request.urlopen`. Loopback
|
|
69
|
+
URLs (`127.0.0.0/8`, `::1`, `localhost`) and `file:`/`data:` URLs pass
|
|
70
|
+
through, so the control-panel tests still serve and probe a real panel.
|
|
71
|
+
Anything else raises `NetworkRefused` before a socket is opened. That is a
|
|
72
|
+
`URLError`, so callers take their no-network path. Each refusal is recorded
|
|
73
|
+
in `NETWORK_ATTEMPTS` with the calling line and the test, and pytest lists
|
|
74
|
+
them in its summary. The wrapper is installed before `src.server` is imported
|
|
75
|
+
and does not need it, so a checkout without the runtime stack is guarded too.
|
|
76
|
+
Installing twice is a no-op, and `uninstall()` puts the original back.
|
|
77
|
+
- `_run_main` sets `DAVINCI_RESOLVE_MCP_UPDATE_CHECK=0`, so the installer tests
|
|
78
|
+
do not ask at all and a clean run records no attempt.
|
|
79
|
+
|
|
80
|
+
### Validation
|
|
81
|
+
|
|
82
|
+
- New `tests/test_offline_network_isolation.py` is the tripwire. It fails if
|
|
83
|
+
`urlopen` is not the guard, if a remote URL (as a string or a `Request`) gets
|
|
84
|
+
through or a loopback one (`127.0.0.1`, `localhost`, `[::1]`) is stopped, if
|
|
85
|
+
`check_for_updates` with its own defaults stops going through the guard, if the
|
|
86
|
+
refusal stops naming `update_check.py … _fetch_latest_release`, or if
|
|
87
|
+
`_run_main` reaches for the network again. The refusal tests put a spy
|
|
88
|
+
downstream of the guard, so a wrong verdict fails the test instead of sending a
|
|
89
|
+
request. With the `_run_main` switch removed, the installer test fails and
|
|
90
|
+
names the URL, the caller and the test. With the guard disabled, all eight tests
|
|
91
|
+
fail in `setUp` before opening any URL. `tests/test_offline_guard.py` now also
|
|
92
|
+
checks that the network guard installs without `src`.
|
|
93
|
+
- Full suite, `python -m unittest discover -s tests -t .`, run behind a
|
|
94
|
+
`sitecustomize` tripwire that records and refuses off-machine `urlopen`,
|
|
95
|
+
DNS lookups and socket connects: 3,747 tests. Off-machine requests went from 1
|
|
96
|
+
on v4.8.4 to 0. The 14 errors are the same tests as on v4.8.4, all
|
|
97
|
+
environmental: six need `numpy` or `requests`, which the venv lacks, and five
|
|
98
|
+
in `test_offline_fallback` need `jszip`, because `node_modules` is not
|
|
99
|
+
installed. The last three are refusals by the tripwire itself: two
|
|
100
|
+
`test_doctor_paths` probe children, and the granular `get_resolve()` →
|
|
101
|
+
`open DaVinci Resolve.app` in `test_granular_destructive_op`, which v4.8.5
|
|
102
|
+
removes. pytest was not run locally.
|
|
103
|
+
- No Resolve behaviour changed, so a live run is not required.
|
|
104
|
+
|
|
5
105
|
## What's New in v4.8.9 — the offline suite's child processes no longer reach Resolve
|
|
6
106
|
|
|
7
107
|
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.11 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
|
|
16
16
|
|
|
17
17
|
一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
|
|
18
18
|
|
|
@@ -157,6 +157,14 @@ The same rule generalises: **"the file round-trips" and "Resolve honours it" are
|
|
|
157
157
|
different claims.** Only a live import establishes the second one. Do not write
|
|
158
158
|
"verified live" in a doc unless a runnable command produced that result.
|
|
159
159
|
|
|
160
|
+
**Changes to `install.py`'s verification or summary must run the installer's live
|
|
161
|
+
probe.** It is the offline suite's one live test, and it is opt-in, because its
|
|
162
|
+
child process reaches the open Resolve past the offline guard:
|
|
163
|
+
|
|
164
|
+
```bash
|
|
165
|
+
RESOLVE_VERIFY=1 venv/bin/python -m unittest tests.test_scripting_lib_discovery.SetupExitStatusTests.test_the_live_probe_agrees_with_the_summary
|
|
166
|
+
```
|
|
167
|
+
|
|
160
168
|
Examples:
|
|
161
169
|
|
|
162
170
|
```bash
|
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.11"
|
|
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.11"
|
|
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()}")
|