<?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/65d4b04917904bc6a6e11f0d5d4d5f3b&quot; frameborder=&quot;0&quot; width=&quot;1113&quot; height=&quot;834&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>834</height><width>1113</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>834</thumbnail_height><thumbnail_width>1113</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/65d4b04917904bc6a6e11f0d5d4d5f3b-eaf72bb8fc049b43.gif</thumbnail_url><duration>45.745</duration><title>Deployment Pipeline Troubleshooting 🛠️</title><description>In this video, I discuss the issues we&apos;re facing with our deployment pipeline. Locally, everything works fine when I specify the node version 20, but it fails in CI. I suspect we need to ensure that node.js is set to version 20 in package.json, even though it&apos;s already specified there. I would appreciate your thoughts on this matter.</description></oembed>