<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Upgrade on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/upgrade/</link><description>Recent content in Upgrade on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 27 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/upgrade/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 15: Upgrading &amp;amp; Migration Strategies (v13 to v21)</title><link>https://ai-blog.noorshomelab.dev/angular-interview-prep-2025/angular-migration-strategies/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-interview-prep-2025/angular-migration-strategies/</guid><description>&lt;h2 id="chapter-15-upgrading--migration-strategies-v13-to-v21"&gt;Chapter 15: Upgrading &amp;amp; Migration Strategies (v13 to v21)&lt;/h2&gt;
&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;As an Angular developer, understanding how to effectively upgrade and migrate applications across major versions is a critical skill, especially in large-scale enterprise environments. This chapter delves into the intricacies of migrating an Angular application from version 13 to the latest stable version, Angular 21, as of late 2025. This significant jump involves navigating multiple breaking changes, new architectural paradigms like standalone components and signals, and evolving tooling.&lt;/p&gt;</description></item><item><title>Meta&amp;#39;s Post-Quantum Cryptography (PQC) Migration Guide</title><link>https://ai-blog.noorshomelab.dev/migrations/meta-pqc-migration-guide/</link><pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/migrations/meta-pqc-migration-guide/</guid><description>&lt;p&gt;&lt;strong&gt;Migration: Classical Cryptography (e.g., RSA, ECC) → NIST PQC Standards (e.g., CRYSTALS-Kyber, CRYSTALS-Dilithium)&lt;/strong&gt;
&lt;strong&gt;Effort estimate:&lt;/strong&gt; Months to years, ongoing for large organizations
&lt;strong&gt;Complexity:&lt;/strong&gt; COMPLETE-REWRITE&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Breaking changes in this upgrade:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Compatibility-breaking changes to encryption protocols and data formats.&lt;/li&gt;
&lt;li&gt;High-risk certificate infrastructure changes affecting trust chains system-wide.&lt;/li&gt;
&lt;li&gt;Fundamental shifts in cryptographic primitives requiring extensive code and system updates.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="why-pqc-migration-is-critical-the-quantum-threat"&gt;Why PQC Migration is Critical (The Quantum Threat)&lt;/h2&gt;
&lt;p&gt;The digital world relies heavily on classical public-key cryptography, such as RSA and Elliptic Curve Cryptography (ECC), to secure communications and data. However, the advent of sufficiently powerful quantum computers poses an existential threat to these foundational cryptographic systems. Algorithms like Shor&amp;rsquo;s algorithm can efficiently break RSA and ECC, while Grover&amp;rsquo;s algorithm can significantly reduce the security of symmetric ciphers and hash functions.&lt;/p&gt;</description></item><item><title>AWS CLI v1 to v2 Migration Guide</title><link>https://ai-blog.noorshomelab.dev/migrations/aws-cli-v1-to-v2-migration-guide/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/migrations/aws-cli-v1-to-v2-migration-guide/</guid><description>&lt;p&gt;&lt;strong&gt;Migration: v1 → v2&lt;/strong&gt;
&lt;strong&gt;Effort estimate:&lt;/strong&gt; 1-2 hours for simple usage, 1-3 days for large codebases with extensive scripting
&lt;strong&gt;Complexity:&lt;/strong&gt; MAJOR&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Breaking changes in this upgrade:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Changes in command syntax and argument parsing (e.g., how parameters are passed)&lt;/li&gt;
&lt;li&gt;Differences in default output formats (e.g., JSON structure, default pagination behavior)&lt;/li&gt;
&lt;li&gt;Behavioral changes in certain commands (e.g., file transfer mechanisms, error handling)&lt;/li&gt;
&lt;li&gt;Changes in how environment variables are interpreted&lt;/li&gt;
&lt;li&gt;Deprecation or removal of specific commands or parameters (identified by migration tools)&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;p&gt;As a migration lead, I understand that upgrading core infrastructure tools like the AWS CLI requires a careful, methodical approach, especially in production environments. This guide outlines a safe and complete path for migrating from AWS CLI v1 to v2, focusing on identifying and resolving breaking changes to ensure a smooth transition.&lt;/p&gt;</description></item><item><title>Migrating to Angular v21: A Comprehensive Checklist</title><link>https://ai-blog.noorshomelab.dev/angular-v21-mastery/chapter-14-migration-guide/</link><pubDate>Wed, 20 Aug 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-v21-mastery/chapter-14-migration-guide/</guid><description>&lt;h2 id="migrating-to-angular-v21-a-comprehensive-checklist"&gt;Migrating to Angular v21: A Comprehensive Checklist&lt;/h2&gt;
&lt;p&gt;Upgrading an Angular application to a new major version can feel daunting, but the Angular team consistently strives to make the process as smooth as possible with robust &lt;code&gt;ng update&lt;/code&gt; schematics. Angular v21 introduces significant internal changes (like zoneless change detection and Vitest), but many are handled automatically or are opt-in.&lt;/p&gt;
&lt;p&gt;This chapter provides a comprehensive checklist and best practices for migrating your existing Angular application to v21.&lt;/p&gt;</description></item></channel></rss>