This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
+1 more
Summary
AI summaryFixed get_keyframes serialization to correctly report time and value for keyframed parameters.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Bugfix | Medium |
Fixes `get_keyframes` serialization to correctly map index to frame position. Fixes `get_keyframes` serialization to correctly map index to frame position. Source: llm_adapter@2026-06-06 Confidence: low |
— |
| Bugfix | Medium |
Corrects `get_keyframes` serialization by treating dict values as frame positions. Corrects `get_keyframes` serialization by treating dict values as frame positions. Source: granite4.1:30b@2026-06-06-audit Confidence: low |
— |
Full changelog
v2.32.2
Fixes fusion_comp(action="get_keyframes") serialization — a follow-up to the add_keyframe fix in v2.32.1.
Fixed
get_keyframesiteratedInput.GetKeyFrames()as if it returned{time: value}, but Fusion returns{1-based index: frame_position}. The result put the keyframe index intimeand the frame position invalue— the actual keyframed values were never reported. The handler now treats the dict values as frame positions and reads each keyframed value back viaGetInput(input_name, frame), returning[{"time": <frame>, "value": <value>}, ...]in frame order.
Validation
- Static checks (import, API parity, CLI
--version,npm pack --dry-run, whitespace) clean. - Unit tests pass (
tests/test_fusion_comp_targeting.py, 10 tests). - Live-validated on DaVinci Resolve Studio 21.0.0: a Transform
Sizekeyed1.0@f0/1.4@f75now serializes as[{"time": 0.0, "value": 1.0}, {"time": 75.0, "value": 1.4}].
Flagged by @sandypoli-boop in #56.
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]