<?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/f51d590a46e8493ebb27be33c63328e6&quot; frameborder=&quot;0&quot; width=&quot;1740&quot; height=&quot;1305&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1305</height><width>1740</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1305</thumbnail_height><thumbnail_width>1740</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f51d590a46e8493ebb27be33c63328e6-00001.gif</thumbnail_url><duration>134.3333333333333</duration><title>Fail CI Build with API Differences</title><description>In this video, I demonstrate how to fail a continuous integration build based on differences between the code and the generated APIs. I show how to store the API in the Smart Bear API store and run tests using GitHub actions. By generating the OpenAPI with AppMap and comparing it to the latest published version from Swagger Hub, we can detect any changes in API functionality. This build failure prevents unwanted API changes from being pushed.</description></oembed>