davinci-resolve-mcp 2.97.4 → 2.97.5
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 +36 -0
- package/README.md +1 -1
- package/README.zh-CN.md +2 -2
- package/docs/process/release-process.md +16 -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,42 @@
|
|
|
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 v2.97.5
|
|
6
|
+
|
|
7
|
+
**`npm ci` was failing outright, and nothing in the release path noticed.**
|
|
8
|
+
No server behavior changed; this is packaging and release-process hardening.
|
|
9
|
+
|
|
10
|
+
### Fixed
|
|
11
|
+
|
|
12
|
+
- **`package-lock.json` was seven releases stale.** It still carried
|
|
13
|
+
`2.90.0`, and — the part that actually broke things — two
|
|
14
|
+
`optionalDependencies` added since then, `js-yaml` and `pg`, were never
|
|
15
|
+
locked. `npm ci` refuses to install at all when the lockfile and
|
|
16
|
+
`package.json` disagree, so every reproducible install path failed with
|
|
17
|
+
`EUSAGE — Missing: js-yaml@4.3.1 from lock file` (plus `pg` and its nine
|
|
18
|
+
transitive deps). CI, fresh contributor clones, and container builds all hit
|
|
19
|
+
it. `npm install` and `npm publish` resolve independently of the lockfile
|
|
20
|
+
and stayed green throughout, which is why it survived seven releases.
|
|
21
|
+
Regenerated with `npm install --package-lock-only`; `npm ci` now installs
|
|
22
|
+
175 packages clean.
|
|
23
|
+
|
|
24
|
+
### Added
|
|
25
|
+
|
|
26
|
+
- **`tests.test_import::test_package_lock_in_sync`** — asserts both version
|
|
27
|
+
fields in the lockfile match `package.json`, and that the root
|
|
28
|
+
`dependencies` / `devDependencies` / `optionalDependencies` blocks match
|
|
29
|
+
exactly. The second half is the one that matters: the version fields being
|
|
30
|
+
right is not evidence `npm ci` works, and dependency drift is what actually
|
|
31
|
+
breaks it. Verified to fail on each drift mode independently.
|
|
32
|
+
|
|
33
|
+
### Changed
|
|
34
|
+
|
|
35
|
+
- `docs/process/release-process.md` lists `package-lock.json` under "Files To
|
|
36
|
+
Update" with the regeneration command, and Required Validation now
|
|
37
|
+
regenerates the lockfile before `test_import` reads it. The lockfile was
|
|
38
|
+
never on the checklist, which is why the drift was never a step anyone
|
|
39
|
+
skipped — it was a step that did not exist.
|
|
40
|
+
|
|
5
41
|
## What's New in v2.97.4
|
|
6
42
|
|
|
7
43
|
**Drift is caught at the edit, not at publish time.** Tooling and docs only —
|
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
|
-
> 本翻译对应 v2.97.
|
|
15
|
+
> 本翻译对应 v2.97.5 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
|
|
16
16
|
|
|
17
17
|
一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
|
|
18
18
|
|
|
@@ -26,6 +26,14 @@ Every release bump must update all version surfaces:
|
|
|
26
26
|
- `src/granular/common.py`
|
|
27
27
|
- `install.py`
|
|
28
28
|
- `package.json`
|
|
29
|
+
- `package-lock.json` — regenerate with `npm install --package-lock-only`, do
|
|
30
|
+
not hand-edit the version. It carries the version in two places and, more
|
|
31
|
+
importantly, the resolved dependency tree. When it disagrees with
|
|
32
|
+
`package.json`, **`npm ci` refuses to install at all** (`EUSAGE — Missing: X
|
|
33
|
+
from lock file`), which breaks CI, fresh clones, and container builds while
|
|
34
|
+
`npm install` and `npm publish` stay green and hide it. The
|
|
35
|
+
`tests.test_import` guard `test_package_lock_in_sync` fails the suite on
|
|
36
|
+
either drift.
|
|
29
37
|
- README version badge
|
|
30
38
|
- README current stats or latest-release summary when they changed
|
|
31
39
|
- `README.zh-CN.md` — the Simplified Chinese translation. Update its version
|
|
@@ -62,6 +70,7 @@ Always run static checks before release:
|
|
|
62
70
|
|
|
63
71
|
```bash
|
|
64
72
|
venv/bin/python tests/test_import.py
|
|
73
|
+
npm install --package-lock-only --no-audit --no-fund # re-stage package-lock.json if it moved
|
|
65
74
|
venv/bin/python scripts/audit_api_parity.py
|
|
66
75
|
venv/bin/python scripts/gen_api_limitations.py --check
|
|
67
76
|
node scripts/agent-rules/generate.mjs --check
|
|
@@ -72,6 +81,13 @@ npm pack --dry-run
|
|
|
72
81
|
git diff --check
|
|
73
82
|
```
|
|
74
83
|
|
|
84
|
+
`test_import` carries `test_package_lock_in_sync`, which is the actual gate on the
|
|
85
|
+
lockfile: it asserts both version fields and the root dependency blocks match
|
|
86
|
+
`package.json`. Run the `npm install --package-lock-only` line above first so the
|
|
87
|
+
regeneration is in the working tree when the test reads it — that ordering is why
|
|
88
|
+
the check is a regeneration followed by a test, not a `git diff --exit-code`,
|
|
89
|
+
which would fire on the release bump's own legitimate change.
|
|
90
|
+
|
|
75
91
|
`test_duplicate_definitions` asserts no module-level name is defined twice under
|
|
76
92
|
`src/`. A second `def foo` silently replaces the first, and in a module the size
|
|
77
93
|
of `src/server.py` the two can be thousands of lines apart with different
|
package/install.py
CHANGED
|
@@ -37,7 +37,7 @@ from src.utils.update_check import (
|
|
|
37
37
|
|
|
38
38
|
# ─── Version ──────────────────────────────────────────────────────────────────
|
|
39
39
|
|
|
40
|
-
VERSION = "2.97.
|
|
40
|
+
VERSION = "2.97.5"
|
|
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
|
@@ -87,7 +87,7 @@ if not logging.getLogger().handlers:
|
|
|
87
87
|
handlers=[logging.StreamHandler()],
|
|
88
88
|
)
|
|
89
89
|
|
|
90
|
-
VERSION = "2.97.
|
|
90
|
+
VERSION = "2.97.5"
|
|
91
91
|
logger = logging.getLogger("davinci-resolve-mcp")
|
|
92
92
|
logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
|
|
93
93
|
logger.info(f"Detected platform: {get_platform()}")
|