https://lab.artur-rios.tech/tags/github-packages/Recent content in GitHub Packages on Artur Rios LabHugoen-usWed, 21 Oct 2026 17:55:00 +0000https://lab.artur-rios.tech/infrastructure/infrastructure-libraries/Wed, 21 Oct 2026 17:55:00 +0000https://lab.artur-rios.tech/infrastructure/infrastructure-libraries/<p>Code that more than one project needs becomes a package. Mine are .NET libraries, published as NuGet packages to two places: <strong>nuget.org</strong>, where anyone finds them, and <strong>GitHub Packages</strong>, next to their source.</p> <table> <thead> <tr> <th>Concern</th> <th>Choice</th> </tr> </thead> <tbody> <tr> <td>Package format</td> <td>NuGet, or the language&rsquo;s own format elsewhere</td> </tr> <tr> <td>Primary feed</td> <td>nuget.org</td> </tr> <tr> <td>Secondary feed</td> <td>GitHub Packages</td> </tr> <tr> <td>Publishing</td> <td>GitHub Actions, on a version tag</td> </tr> <tr> <td>Versioning</td> <td>Semantic versioning</td> </tr> </tbody> </table> <h2 id="package-metadata">Package metadata<a class="heading-anchor" href="#package-metadata" aria-label="Link to this section"></a></h2> <p>The project file describes the package, so <code>dotnet pack</code> produces a complete <code>.nupkg</code> with its symbols alongside:</p>