davinci-resolve-mcp 4.8.10 → 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 CHANGED
@@ -2,6 +2,48 @@
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
+
5
47
  ## What's New in v4.8.10 — the offline suite no longer asks GitHub for the latest release
6
48
 
7
49
  No tool, action or runtime behaviour changed. This release changes the test
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  English | [简体中文](README.zh-CN.md)
4
4
 
5
- [![Version](https://img.shields.io/badge/version-4.8.10-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
5
+ [![Version](https://img.shields.io/badge/version-4.8.11-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
6
6
  [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
7
7
  [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
8
8
  [![Tools](https://img.shields.io/badge/MCP%20Tools-37%20(389%20full)-blue.svg)](#server-modes)
package/README.zh-CN.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  [English](README.md) | 简体中文
4
4
 
5
- [![Version](https://img.shields.io/badge/version-4.8.10-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
5
+ [![Version](https://img.shields.io/badge/version-4.8.11-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
6
6
  [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
7
7
  [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
8
8
  [![Tools](https://img.shields.io/badge/MCP%20Tools-37%20(389%20full)-blue.svg)](#服务器模式)
@@ -12,7 +12,7 @@
12
12
  [![Python](https://img.shields.io/badge/python-3.10+-green.svg)](https://www.python.org/downloads/)
13
13
  [![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
14
14
 
15
- > 本翻译对应 v4.8.10 版 README。如与英文原版有出入,以 [英文原版](README.md) 为准。
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.10"
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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "davinci-resolve-mcp",
3
- "version": "4.8.10",
3
+ "version": "4.8.11",
4
4
  "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
5
5
  "license": "MIT",
6
6
  "author": "Samuel Gursky <samgursky@gmail.com>",
@@ -93,7 +93,7 @@ if not logging.getLogger().handlers:
93
93
  handlers=[logging.StreamHandler()],
94
94
  )
95
95
 
96
- VERSION = "4.8.10"
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()}")
package/src/server.py CHANGED
@@ -11,7 +11,7 @@ Usage:
11
11
  python src/server.py --full # Start the 377-tool granular server instead
12
12
  """
13
13
 
14
- VERSION = "4.8.10"
14
+ VERSION = "4.8.11"
15
15
 
16
16
  import base64
17
17
  import os