davinci-resolve-mcp 4.8.13 → 4.8.15

package/CHANGELOG.md

@@ -2,6 +2,48 @@
 
 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.
 
+## What's New in v4.8.15 — `background="false"` runs synchronously
+
+### Fixed
+
+- **`_run_maybe_background` decided sync-versus-background with bare truthiness on
+  `background` and `async_job`.** ([#265](https://github.com/samuelgursky/davinci-resolve-mcp/pull/265), @Dev-next-gen)
+  A caller sending `background="false"` (or `"no"`, `"0"`, `"off"`) to any action that
+  offers a background job got a background job anyway, with a `job_id` instead of the
+  result they asked for synchronously. Both parameters now go through `_coerce_bool`,
+  like every other boolean read fixed this month; the two media-analysis readers of the
+  same flag already went through their own coercer. Real booleans and the true
+  spellings are unchanged. Guard test: six false spellings on both parameter names,
+  twelve subtests failing on the previous code.
+
+## What's New in v4.8.14 — both dependency trees read zero advisories again
+
+### Changed
+
+- **`npm audit` read eight advisories across the two manifests; all eight clear
+  inside the ranges already declared.** Root (6: 3 high, 3 moderate):
+  `@hono/node-server` 1.19.14 -> 2.1.1, `hono` 4.12.26 -> 4.13.8, `adm-zip`
+  0.6.0 -> 0.6.1, `fast-uri` 3.1.2 -> 3.1.8, `ip-address` 10.2.0 -> 10.7.2,
+  `qs` 6.15.2 -> 6.16.0. `resolve-advanced` (2: 1 high, 1 moderate): `adm-zip`
+  and `qs` to the same versions, applied with `--package-lock-only` because
+  that package has no `node_modules` on this machine. Only the lockfiles move;
+  neither `package.json` needed a new range.
+- **The advisories v2.212.4 had to park are among them.** That entry recorded
+  five transitive ones — hono, @hono/node-server, ajv -> fast-uri,
+  express-rate-limit -> ip-address, express -> qs — as clearing "only when the
+  SDK bumps its own dependencies". The SDK has since done so, and the two
+  adm-zip advisories, which are a direct dependency, clear with 0.6.1.
+
+### Validation
+
+- Full offline Python suite under both runners, macOS, Python 3.10:
+  `python -m unittest discover -s tests -t .` and `python -m pytest tests -q`.
+- `npm ci` from the root lockfile, `npm run smoke` (reports 4.8.14) and
+  `npm run pack:check`; `npm audit` reports zero on both manifests afterwards.
+- No runtime code changed, so no live Resolve check was needed. The
+  `resolve-advanced` Node suite was not run: its dependencies are not installed
+  here, and its lockfile change is the same two packages as the root's.
+
 ## What's New in v4.8.13 — `include_linked="false"` no longer relinks
 
 ### Fixed

package/README.md

@@ -2,7 +2,7 @@
 
 English | [简体中文](README.zh-CN.md)
 
-[![Version](https://img.shields.io/badge/version-4.8.13-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-4.8.15-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
 [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
 [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
 [![Tools](https://img.shields.io/badge/MCP%20Tools-37%20(389%20full)-blue.svg)](#server-modes)

package/README.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](README.md) | 简体中文
 
-[![Version](https://img.shields.io/badge/version-4.8.13-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-4.8.15-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
 [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
 [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
 [![Tools](https://img.shields.io/badge/MCP%20Tools-37%20(389%20full)-blue.svg)](#服务器模式)
@@ -12,7 +12,7 @@
 [![Python](https://img.shields.io/badge/python-3.10+-green.svg)](https://www.python.org/downloads/)
 [![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
-> 本翻译对应 v4.8.13 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
+> 本翻译对应 v4.8.15 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
 
 一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
 

package/install.py

@@ -37,7 +37,7 @@ from src.utils.update_check import (
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "4.8.13"
+VERSION = "4.8.15"
 # Only hard floor: mcp[cli] requires Python 3.10+. There is no upper bound —
 # Resolve's scripting bridge loads into newer interpreters on recent builds
 # (Python 3.14 verified against Resolve Studio 20.3.2). Older Resolve builds

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "davinci-resolve-mcp",
-  "version": "4.8.13",
+  "version": "4.8.15",
   "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
   "license": "MIT",
   "author": "Samuel Gursky <samgursky@gmail.com>",

package/src/granular/common.py

@@ -93,7 +93,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "4.8.13"
+VERSION = "4.8.15"
 logger = logging.getLogger("davinci-resolve-mcp")
 logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
 logger.info(f"Detected platform: {get_platform()}")

package/src/server.py

@@ -11,7 +11,7 @@ Usage:
     python src/server.py --full       # Start the 377-tool granular server instead
 """
 
-VERSION = "4.8.13"
+VERSION = "4.8.15"
 
 import base64
 import os
@@ -1790,7 +1790,7 @@ def _run_maybe_background(label: str, params: Dict[str, Any], fn):
     job and return its id at once; otherwise run fn inside long_resolve_op and
     return its result, preserving the synchronous contract.
     """
-    if params.get("background") or params.get("async_job"):
+    if _coerce_bool(params.get("background")) or _coerce_bool(params.get("async_job")):
         job_id = background_jobs.start_job(label, fn)
         return {
             "success": True,