<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Canary Releases on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/canary-releases/</link><description>Recent content in Canary Releases on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 11 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/canary-releases/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 14: Deployment and CI/CD for React Applications</title><link>https://ai-blog.noorshomelab.dev/react-production-guide-2026/deployment-cicd-react/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/react-production-guide-2026/deployment-cicd-react/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 14! So far, we&amp;rsquo;ve built robust, performant, and secure React applications. But what good is a fantastic application if no one can use it reliably? This chapter is all about getting your React app out into the world and keeping it running smoothly.&lt;/p&gt;
&lt;p&gt;Here, we&amp;rsquo;ll dive deep into &lt;strong&gt;Deployment&lt;/strong&gt; and &lt;strong&gt;Continuous Integration/Continuous Delivery (CI/CD)&lt;/strong&gt;. You&amp;rsquo;ll learn how to automate the process of building, testing, and releasing your React application, ensuring every change you make is delivered to your users quickly and safely. We&amp;rsquo;ll explore why these practices are non-negotiable for modern software development, the common pitfalls to avoid, and how to implement them step-by-step using industry-standard tools.&lt;/p&gt;</description></item></channel></rss>