This release includes breaking changes for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+1 more
Summary
AI summaryFixes analyzed‑clip count under‑count after Media Pool rename and adds persisted clip index for stable ID mapping.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Low |
Adds persisted `clips/index.json` mapping stable IDs to report folders for robust counting. Adds persisted `clips/index.json` mapping stable IDs to report folders for robust counting. Source: llm_adapter@2026-06-02 Confidence: high |
— |
| Bugfix | Medium |
Fixes analyzed clip count under‑count after Media Pool rename. Fixes analyzed clip count under‑count after Media Pool rename. Source: llm_adapter@2026-06-02 Confidence: high |
— |
| Bugfix | Medium |
Fixes cross‑basis mismatch of folder hashes between Resolve inventory and batch jobs. Fixes cross‑basis mismatch of folder hashes between Resolve inventory and batch jobs. Source: llm_adapter@2026-06-02 Confidence: high |
— |
| Bugfix | Medium |
Prevents creation of orphaned duplicate report folders when re‑analyzing renamed clips. Prevents creation of orphaned duplicate report folders when re‑analyzing renamed clips. Source: llm_adapter@2026-06-02 Confidence: high |
— |
Full changelog
v2.27.2
Fixes the control panel under-counting analyzed clips after a Media Pool rename (issue #51), and hardens how analysis reports are matched to clips.
Fixed
- Analyzed-count under-count after rename (#51). Report folders are named
<display-slug>-<hash>, but the count only recognized a report when the folder name matched the clip's current display name. A fully analyzed project (e.g. 303/303 reports on disk) could show as 108/303 after clips were renamed. The count now matches on the rename-stable hash (and the ids inside each report) on both the disk path and the jobs-DB fallback. - Cross-basis mismatch. The folder hash was a
clip_id-first cascade, so the same media hashed differently depending on which fields a record carried — Resolve inventory (clip_id) vs path-based batch jobs (file path). The hash is now anchored to the normalized file path, so both agree on one folder. Legacy folders (clip_id- or raw-path-based) still resolve via a migration-safe candidate-hash set, so no on-disk migration is required. - Orphaned duplicate folders. Re-analyzing a renamed clip now reuses its existing report folder instead of minting a new
<newslug>-<hash>directory.
Added
- Persisted clip index (
clips/index.json) mapping every stable id found in a report (normalized + raw file path, clip_id, media_id) to its folder, so the count can match a clip by any id it still carries — including an offline clip that no longer reports a file path but retains its clip_id. The index is refreshed only when a report is added, removed, or rewritten (cheap signature check), keeping the recurring poll inexpensive.
No public MCP tool surface changed.
Validation
tests/test_import.py,scripts/audit_api_parity.py,node bin/davinci-resolve-mcp.mjs --help/--version,npm pack --dry-run,git diff --check— all clean.- 149 unit tests pass across
test_media_analysis,test_analysis_runs,test_analysis_caps,test_caps_integration,test_provenance, including new coverage for rename, cross-basis, legacy-folder reuse, the jobs-DB fallback, and the offline/no-path case. - No DaVinci Resolve scripting behavior changed (the fix is local report-folder resolution); live Resolve validation 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
Related context
Beta — feedback welcome: [email protected]