video1.0<iframe src="https://www.loom.com/embed/ebfdaee0363449a784fb7030c3bb0d02" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/ebfdaee0363449a784fb7030c3bb0d02-986307686644e662.gif163.243This Loom explains the Test and Fix Obsidian Linear release pipeline and how the team validated release behavior using a separate test repository. The author runs a GitHub workflow against a specific branch, then iteratively fixes five out of six detected issues, documenting detailed verification steps tied to release provenance and the GitHub run. The remaining unfixable item is a commit version bug, and a proposed approach to updating package.json and manifest.json in the monorepo was reconsidered due to GitHub ActionBot write permissions, leading to a recommendation to comment out that step. The author confirms that the ticket was added correctly to the current in-progress release on the first run and that a stable test created a new release on the Linear side.