<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/1c2c8bbce50a4d3d8cfe727c2d5edfb3&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/1c2c8bbce50a4d3d8cfe727c2d5edfb3-a41c46d817a42df1.gif</thumbnail_url><duration>109.099</duration><title>Setting Up Linear Release for Obsidian</title><description>This Loom sets up a Linear-triggered linear release pipeline for publishing to Obsidian. It describes a release-complete YAML called from Linear along with a release script that configures environments and runs the publish script with versioning. The author tested the setup by running it on every push to the branch, confirming that the “Publish to Obsidian” call succeeds and the release steps complete, including checking that the Obsidian release was created. Finally, they validate the sync feature by installing VIABRAT using the published version with TESS and verifying that importing still works when sync is enabled.</description></oembed>