{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/d2db4a4879a046ae8560c5c6f040aa15\" frameborder=\"0\" width=\"1680\" height=\"1260\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1260,"width":1680,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1260,"thumbnail_width":1680,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/d2db4a4879a046ae8560c5c6f040aa15-4ca29728281a904d.gif","duration":205.227,"title":"Prototype for Custom Package Versioning","description":"This Loom previews a prototype to add multi-version support for PDQ custom packages, similar to how production packages work today. Currently, custom packages only allow editing a single version, and changes update that version without saving a new one, so users often create multiple similarly named packages instead. The prototype adds a versions list showing the version number, release date, whether it supports Windows, Mac, or both, and when it was last updated, with clicking taking you to the deployment. It also demonstrates an add-version flow where the user enters a version, the UI duplicates the previous latest version’s steps for both Windows and Mac, and the saved version appears as an available deployment and automation reference."}