<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mudith Akshura on Medium]]></title>
        <description><![CDATA[Stories by Mudith Akshura on Medium]]></description>
        <link>https://medium.com/@mudith.akshura23?source=rss-b06f28e63c2c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*0XZPx1hVEQIV9AYL</url>
            <title>Stories by Mudith Akshura on Medium</title>
            <link>https://medium.com/@mudith.akshura23?source=rss-b06f28e63c2c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:30:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mudith.akshura23/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Stop Manually Updating NuGet Versions: A GitHub Actions Versioning Strategy That Just Works]]></title>
            <link>https://medium.com/@mudith.akshura23/stop-manually-updating-nuget-versions-a-github-actions-versioning-strategy-that-just-works-450a5e97055c?source=rss-b06f28e63c2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/450a5e97055c</guid>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[nuget-package]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[package-version]]></category>
            <dc:creator><![CDATA[Mudith Akshura]]></dc:creator>
            <pubDate>Tue, 11 Aug 2026 10:41:31 GMT</pubDate>
            <atom:updated>2026-08-11T10:41:31.001Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pVMOBw58No7RdOvCuHlJhA.png" /></figure><p><em>How I automated versioning for my .NET libraries and never worried version numbers again.</em></p><p>Every Developer has done this.</p><p>You make a small change.</p><p>Run the tests.</p><p>Everything passes.</p><p>Publish the NuGet package.</p><p><em>A few minutes later …</em></p><p>Someone asks</p><blockquote>“Did you update the version?”</blockquote><p>You didn’t.</p><p>Now you’re deleting packages, creating new tags, updating the project file, and republishing.</p><p>Sound familiar?</p><p>I got tired of repeating the same manual steps every release.</p><p>There had to be a better way.</p><h3>The Problem</h3><p>Most .NET libraries still keep their version inside the project file.</p><pre>&lt;Version&gt;1.0.19&lt;/Version&gt;</pre><p>Every release means someone has to remember to update it.</p><p>That creates problems.</p><ul><li>Forgotten version bumps</li><li>Duplicate package versions.</li><li>Merge conflicts.</li><li>Hotfix confusion.</li><li>Extra pull requests just for the version update.</li></ul><p>The larger the team becomes, the worse it gets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RWtpy8K7TFh8aTBfTe45bw.png" /><figcaption>Manual Versioning</figcaption></figure><h3>What I Wanted</h3><p>My requirements were simple.</p><p>✅ Developers should never edit version numbers.</p><p>✅ GitHub Actions should decide the version.</p><p>✅ Releases should use Git tags.</p><p>✅ Pull requests should produce preview packages.</p><p>✅ Every package should be traceable back to a commit.</p><h3>The Solution</h3><p>Instead of storing the version inside the project, I moved the responsibility into the CI pipeline.</p><p>Now GitHub Actions decides everything.</p><p>When a release tag exists</p><blockquote>v1.2.0</blockquote><p>the package becomes</p><blockquote>1.2.0</blockquote><p>When it’s a pull request</p><blockquote>1.2.0-dev.154</blockquote><p>When it’s the main branch</p><blockquote>1.2.0-ci.248</blockquote><p>No manual editing.</p><p>No forgotten version updates.</p><p>No duplicate packages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WUwqEadFJeLnlun_2VboNg.png" /><figcaption>Automatic Version Resolution Flow</figcaption></figure><h3>How the Pipeline Thinks</h3><p>The logic is surprisingly simple.</p><p>Is this a Tag?</p><p>Yes</p><p>⬇️</p><p>Release Version</p><p>No</p><p>⬇️</p><p>Is this Pull Request?</p><p>Yes</p><p>⬇️</p><p>Preview Package</p><p>No</p><p>⬇️</p><p>Development Build</p><p>That tiny decision tree completely automates the release process.</p><h3>Why This Is Better</h3><p>The biggest benefit isn’t convenience.</p><p>It’s consistency.</p><p>Every package tells a story.</p><ul><li>1.0.19 — Official release</li><li>1.0.19-dev.42 — Pull request build</li><li>1.0.19.327 — Main branch build</li></ul><p>You instantly know where package came from.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FZ1qCX0BibfkonS03JMXyg.png" /><figcaption>Version Number Flow</figcaption></figure><h3>The Best Part</h3><p>Developers no longer think about versions.</p><p>They simply write code.</p><p>GitHub Actions handles</p><ul><li>Package Version</li><li>Assembly Version</li><li>File Version</li><li>Informational Version</li></ul><p>The build pipeline becomes the single source of truth.</p><h3>Lessons Learned</h3><p>I used to think versioning was just another property inside a <em>.csproj</em></p><p>It isn’t.</p><p>It’s part of your delivery process.</p><p>Moving version management into CI made releases,</p><ul><li>Faster</li><li>More reliable</li><li>Easier to audit</li><li>Easier to reproduce</li></ul><p>More importantly, it removed one more manual step from every deployment.</p><h3>Final Thoughts</h3><p>The best automation is the automation developers forget exists.</p><p>Nobody enjoys opening a project file just to change</p><pre>&lt;Version&gt;1.0.20&lt;/Version&gt;</pre><p>before every release</p><p>That work belongs to the pipeline, not the developer.</p><p>Once versioning became automatic, publishing NuGet packages became something I could trust instead of something I had to double check.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jErv7Umn7kXFD6ZSD6KSxg.png" /><figcaption>Final Version of Pipeline</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=450a5e97055c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Thought Supporting .NET 8 and .NET 10 Would Take 10 Minutes. I Was Wrong.]]></title>
            <link>https://medium.com/@mudith.akshura23/i-thought-supporting-net-8-and-net-10-would-take-10-minutes-i-was-wrong-b951c90cc26d?source=rss-b06f28e63c2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b951c90cc26d</guid>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[dot-net-framework]]></category>
            <category><![CDATA[dotnet-core]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <dc:creator><![CDATA[Mudith Akshura]]></dc:creator>
            <pubDate>Thu, 06 Aug 2026 09:44:20 GMT</pubDate>
            <atom:updated>2026-08-06T10:02:16.953Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d2tF7_DlNqUNJyTAb-m0dw.png" /></figure><p><em>How one confusing CI error taught me that designing the pipeline matters more than writing the YAML.</em></p><h3><strong>The plan was pretty simple</strong></h3><p>I was building a reusable authentication library that needed to support both <strong>.NET 8</strong> and <strong>.NET 10</strong></p><p>The CI pipeline sounded straightforward.</p><ul><li><em>Restore dependencies</em></li><li><em>Build the solution</em></li><li><em>Run tests</em></li><li><em>Pack the NuGet package</em></li><li><em>Upload the artifacts</em></li></ul><p>Since the library targeted two frameworks, GitHub Actions Matrix strategy seemed like the obvious choice.</p><p>One job for .NET 8</p><p>One job for .NET 10</p><p>Simple.</p><p>Or so I thought</p><h3>Then the Pipeline Failed …</h3><p>The build completed successfully.</p><p>The tests passed.</p><p>The DLLs were generated exactly where they should be.</p><p>Yet the packaging step failed with this error</p><pre>NU5026: The file bin/Release/net10.0/MyLibrary.dll was not found.</pre><p>I checked the logs again.</p><p>This was the .NET 8 job.</p><p>Why was it looking for a .NET 10 DLL?</p><p>Surely that had to be a mistake.</p><p>Then I opened the logs for the .NET 10 job.</p><pre>NU5026: The file bin/Release/net8.0/MyLibrary.dll was not found.</pre><p>Now I had two jobs.</p><p>Each one was looking for the other framework’s output.</p><p>I felt like they had swapped brains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*6-T3sotMufRTWu1bQYgh1A.png" /><figcaption>The Confusing Failure.</figcaption></figure><h3>The Build Wasn’t the Problem</h3><p>The first thing I doubted was build itself.</p><p>But the logs told a different story.</p><p>✅Build succeeded.</p><p>✅net 8.0</p><p>✅net 10.0</p><p>Even the output folders were correct.<br>bin/<br> | — net8.0/Library.dll<br> | — net10.0/ Library.dll</p><p>So why was <strong>Pack </strong>insisting those files didn’t exist?</p><p>That’s when I discovered something I had never paid much attention to before.</p><p><strong><em>dotnet build</em></strong> and <strong><em>dotnet pack</em></strong> don’t always behave the same especially when you’re working with <strong>muti-targeted projects.</strong></p><h3>The Rabbit Hole</h3><p>My Project targeted both frameworks.</p><pre>&lt;TargetFrameworks&gt;net8.0;net10.0&lt;/TargetFrameworks&gt;</pre><p>The matrix job only built one framework at a time.</p><p>However, the packaging step was still evaluation the project as a <strong>muti-targeted</strong> library.</p><p>That tiny difference completely changed the behavior.</p><p>I spent hours trying different combinations of</p><ul><li><strong><em>- -no-build</em></strong></li><li><strong><em>-f</em></strong></li><li><strong><em>TargetFramework</em></strong></li><li><strong><em>GeneratePackageOnBuild</em></strong></li></ul><p>Every change fixed one issue and introduced another.</p><p>At one point I realized something important.</p><p>I wasn’t debugging YAML anymore.</p><p>I was debugging my architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*rXftVTYFIk8HYa0PHfDRlg.png" /><figcaption>How Multi-Target Projects Are Evaluated.</figcaption></figure><h3>The Real Problem</h3><p>Initially, every matrix job tried to do everything.</p><p>Restore ➡️ Build ➡️ Test ➡️ Pack</p><p>It looked clean.</p><p>But it mixed two very different responsibilities.</p><p>Testing answers one question,</p><blockquote>Does each target framework work correctly?</blockquote><p>Packaging answers another</p><blockquote>Can I produce one distributable NuGet package containing every supported framework?</blockquote><p>Those aren’t the same job.</p><p>Trying to make one workflow do both was what made everything complicated.</p><h3>The Solution</h3><p>Instead of fighting the tooling, I changed the design.</p><p>I split the pipeline into two clear responsibilities.</p><p><strong>Job 1 — Validate Every Framework</strong></p><p>A matrix strategy builds and tests each framework independently.</p><p>Matrix Leg 01 (.NET 8) — Restore ➡️ Build ➡️ Test</p><p>Matrix Leg 02 (.NET 10) — Restore ➡️ Build ➡️ Test</p><p>Each framework produces its own test results, coverage reports, and build logs.</p><p>If one fails, the other still completes.</p><p>Job 2— Package Once</p><p>After every validation job suceeds, a seperate packaging job creates <strong>one </strong>multi-target NuGet package.</p><p>Restore ➡️ Build All Frameworks ➡️ Pack ➡️ Publish into GitHub Actions Artifacts</p><p>This keeps validation independent while ensuring consumers receive a single package that supports bot <strong>.NET 8</strong> and <strong>.NET 10</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*mHrQsGINuuEgNjJINr8dNA.png" /><figcaption>Old vs New Pipeline Architecture</figcaption></figure><h3>The Result</h3><p>The final workflow became much simpler.</p><ul><li>✅ Independent framework validation</li><li>✅ Parallel builds</li><li>✅ Reliable test reporting</li><li>✅ One muti-target NuGet package</li><li>✅ Cleaner GitHub Actions workflow</li><li>✅ Easier troubleshooting</li></ul><p>Sometimes the best Optimization is not adding another command.</p><p>It’s removing responsibility from the wrong place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eNX0vAbNf1y0AuDWfkPnRg.png" /><figcaption>Final GitHub Actions Workflow</figcaption></figure><h3>What I learned</h3><p>This experience reminded me of something that’s easy to forget.</p><p>When automation becomes difficult, don’t immediately blame tools.</p><p>Question the design first.</p><p>The problem wasn’t GitHub Actions.</p><p>It wasn’t MSBuild.</p><p>It wasn’t even <strong><em>dotnet pack.</em></strong></p><p>The problem was that I was asking one workflow to solve 2 different problems.</p><p>Once I separated validation form distribution, everything became simpler.</p><h3>Final Thoughts</h3><p>CI/CD isn’t just automation.</p><p>It’s software archtiecture written in YAML.</p><p>The commands matter.</p><p>The tools matter.</p><p>But the biggest improvements often come from stepping back and asking a simple question,</p><blockquote>Am I solving the right problem in the right place?</blockquote><p>That one question completely changed how I design build pipelines, and it is a lesson I’ll carry into every project I build from now on.</p><p><em>Have you ever lost hours chasing a CI/CD issue that turned out to be an architectural problem rather than a tooling problem? I’d love to hear your experience in the comments.</em></p><p>References — <a href="https://ilirivezaj.com/tutorials/github-actions-cicd">https://ilirivezaj.com/tutorials/github-actions-cicd</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b951c90cc26d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>