Skip to content

samuelgursky/davinci-resolve-mcp

v2.37.1 Maintenance

This release keeps dependencies and maintenance posture current for teams operating this tool.

Published 1mo MCP Developer Tools
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

blackmagic blackmagic-design blackmagicdesign davinci-resolve davinciresolve mcp
+1 more
mcp-server

Summary

AI summary

Minor fixes and improvements.

Changes in this release

Dependency Low

Runner actions upgraded to Node 24 majors ahead of GitHub's June 16 2026 enforcement date.

Runner actions upgraded to Node 24 majors ahead of GitHub's June 16 2026 enforcement date.

Source: llm_adapter@2026-06-09

Confidence: high

Bugfix Medium

Legacy live-harness scripts now skip cleanly when Resolve is unavailable, avoiding pytest collection crashes.

Legacy live-harness scripts now skip cleanly when Resolve is unavailable, avoiding pytest collection crashes.

Source: llm_adapter@2026-06-09

Confidence: high

Bugfix Medium

pytest no longer mis-collects `test_resolve20_api.py`'s internal `test()` helper; it is renamed to `run_live_check()`.

pytest no longer mis-collects `test_resolve20_api.py`'s internal `test()` helper; it is renamed to `run_live_check()`.

Source: llm_adapter@2026-06-09

Confidence: high

Bugfix Medium

Batch-CLI synthetic-job test no longer depends on installed transcription backends.

Batch-CLI synthetic-job test no longer depends on installed transcription backends.

Source: llm_adapter@2026-06-09

Confidence: high

Bugfix Medium

npm publish workflow stops failing when a consumed OIDC token causes retry errors, verifying tarball shasum instead.

npm publish workflow stops failing when a consumed OIDC token causes retry errors, verifying tarball shasum instead.

Source: llm_adapter@2026-06-09

Confidence: high

Full changelog

v2.37.1

Test-suite hygiene and CI reliability. No DaVinci Resolve behavior changed.

Fixed

  • The legacy live-harness scripts (test_all_tools, test_phase2test_phase5) exited at import when Resolve was unavailable, crashing pytest collection and surfacing as five loader errors under unittest discovery. They now skip cleanly under both runners while keeping the hard-exit behavior when run as standalone scripts. (Adapted from a contribution by @diesdaas — thanks!)
  • pytest mis-collected test_resolve20_api.py's internal test() helper as a test function; renamed to run_live_check().
  • The batch-CLI synthetic-job test no longer depends on which transcription backends the host has installed.

CI

  • The npm publish workflow no longer reports failure when the registry accepted the publish but npm's retried request re-presented a consumed OIDC token; it verifies the published tarball shasum before failing.
  • Runner actions bumped to their Node 24 majors ahead of GitHub's June 16, 2026 forcing date.

Validation

  • Offline unit suite fully clean under both runners for the first time: unittest discovery 1,019 tests / 0 errors / 5 clean skips; pytest collection 19 passed / 5 skipped on the touched files. Standalone script behavior verified unchanged.
  • No Resolve behavior changed; live test not required.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track samuelgursky/davinci-resolve-mcp

Get notified when new releases ship.

Sign up free

About samuelgursky/davinci-resolve-mcp

MCP server integration for DaVinci Resolve

All releases →

Beta — feedback welcome: [email protected]