davinci-resolve-mcp 4.6.2 → 4.6.3
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 +20 -0
- package/README.md +1 -1
- package/README.zh-CN.md +2 -2
- package/docs/process/release-process.md +10 -1
- 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,26 @@
|
|
|
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.6.3 — the publish workflow keeps npm `latest` on the highest version
|
|
6
|
+
|
|
7
|
+
Release-process hardening only. No tool, action, or Resolve behaviour changed.
|
|
8
|
+
|
|
9
|
+
### Fixed
|
|
10
|
+
|
|
11
|
+
- **Three release tags pushed in one command left npm `latest` on the oldest of
|
|
12
|
+
them.** The `Publish npm package` runs for v4.6.0, v4.6.1 and v4.6.2 executed in
|
|
13
|
+
parallel and finished in the order 4.6.1, 4.6.2, 4.6.0; npm points `latest` at
|
|
14
|
+
whichever publish lands last, so `npm install davinci-resolve-mcp` resolved to
|
|
15
|
+
4.6.0 while v4.6.2 was the GitHub Release marked latest. The workflow now ends with
|
|
16
|
+
a step that compares `dist-tags.latest` against the highest published version
|
|
17
|
+
(always counting the version the run itself carries, because `npm view` can serve
|
|
18
|
+
a document minutes stale right after a publish) and re-points `latest` when it
|
|
19
|
+
lags. It never fails the job; if the trusted-publishing token cannot edit
|
|
20
|
+
dist-tags it logs the `npm dist-tag add` command for a maintainer. This release's
|
|
21
|
+
own publish is what puts `latest` back on the newest version.
|
|
22
|
+
- `docs/process/release-process.md`: push one release tag at a time and wait for its
|
|
23
|
+
publish run before pushing the next; the workflow step is a backstop, not the plan.
|
|
24
|
+
|
|
5
25
|
## What's New in v4.6.2 — the granular server's macOS temp-path redirect matches the compound server's
|
|
6
26
|
|
|
7
27
|
### Fixed
|
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.6.
|
|
15
|
+
> 本翻译对应 v4.6.3 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
|
|
16
16
|
|
|
17
17
|
一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
|
|
18
18
|
|
|
@@ -204,7 +204,16 @@ should say that no behavior changed.
|
|
|
204
204
|
```
|
|
205
205
|
|
|
206
206
|
6. Push `main`.
|
|
207
|
-
7. Create and push the annotated tag
|
|
207
|
+
7. Create and push the annotated tag. **Push one release tag at a time and wait
|
|
208
|
+
for its `Publish npm package` run to finish before pushing the next.** Runs for
|
|
209
|
+
tags pushed together execute in parallel, and npm points `latest` at whichever
|
|
210
|
+
publish finishes *last*: on 2026-09-15 v4.6.0–v4.6.2 pushed in one command
|
|
211
|
+
finished in the order 4.6.1, 4.6.2, 4.6.0, and `latest` landed on 4.6.0. The
|
|
212
|
+
workflow's final step now re-points `latest` at the highest published version
|
|
213
|
+
when it lags, but it is a backstop, not the plan — the trusted-publishing token
|
|
214
|
+
may not be allowed to edit dist-tags, in which case the fix is
|
|
215
|
+
`npm dist-tag add davinci-resolve-mcp@X.Y.Z latest` by a logged-in maintainer,
|
|
216
|
+
or simply the next release's publish, which sets `latest` itself.
|
|
208
217
|
|
|
209
218
|
```bash
|
|
210
219
|
git tag -a v2.4.1 -m "v2.4.1"
|
package/install.py
CHANGED
|
@@ -37,7 +37,7 @@ from src.utils.update_check import (
|
|
|
37
37
|
|
|
38
38
|
# ─── Version ──────────────────────────────────────────────────────────────────
|
|
39
39
|
|
|
40
|
-
VERSION = "4.6.
|
|
40
|
+
VERSION = "4.6.3"
|
|
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.6.
|
|
96
|
+
VERSION = "4.6.3"
|
|
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()}")
|