<?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/b1ffce184d64469ca92a3d9c9e1db008&quot; frameborder=&quot;0&quot; width=&quot;2124&quot; height=&quot;1593&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1593</height><width>2124</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1593</thumbnail_height><thumbnail_width>2124</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b1ffce184d64469ca92a3d9c9e1db008-bf5e5be24d8d1645.gif</thumbnail_url><duration>669.019</duration><title>Outdated Gems Audit Process Explained 🛠️</title><description>In this video, I walk you through how to use the outdated gems audit script found in our repo, which scans for outdated gems in our application. By running the script, it fetches data from the RubyGems API, formats it into a CSV, and opens a new Google Sheet for easy analysis. I demonstrate how to manipulate the data, create a pivot table, and prioritize updates based on versioning and release dates. I encourage you to regularly run this audit to keep our dependencies up to date and manageable. Please take action on the gems listed, especially those in development and test groups, as they are generally safer to update.</description></oembed>