semantic-release-nuget v1.1.0
Up a Level
Last week, I wrote semantic-release-dotnet[1] which was a semantic-release[2] plugin to automatically set the version to the appropriate one before building.
2: https://semantic-release.gitbook.io/semantic-release/ (https://semantic-release.gitbook.io)
One of the key parts missing from the normal .NET development cycle was also publishing the packages. I decided to break that into a separate plugin because I have a number of places where I don't want to publish but I do want something versioned (internal projects and customized deployments). So, in the essence of the Single Responsibility Principle[3], I created a second utility which does one thing: build and publish NuGet packages.
Introducing semantic-release-nuget[4]. It doesn't have a lot of configurations, but the documentation covers all of them. Basically, it does one thing.
I mostly tested with MfGames.Locking[5], my CIL library for some thread-locking patterns, because I'm the process of carving out Gallium[6] and Nitride[7] into their own packages. I'm just not sure where to put them, so they are probably going in my Gitlab[8] organization until I find a “better” organization/home.
6: /tags/gallium/
7: /tags/nitride/
8: https://gitlab.com/mfgames-cil/ (https://gitlab.com)
Metadata
Categories:
Tags:
MfGames.Locking
MyGet
NuGet
semantic-release
semantic-release-dotnet
semantic-release-nuget
Single Responsibility Principle
Footer
Below are various useful links within this site and to related sites (not all have been converted over to Gemini).
Contact
Biography
Bibliography
Support
Fedran (fedran.com)
Coding (https://mfgames.com)
The Moonfires (https://moonfire.us)
Tags
Colophon
License
Response: 20 (Success), text/gemini
| Original URL | gemini://d.moonfire.us/blog/2021/09/04/semantic-release-nuget/ |
|---|---|
| Status Code | 20 (Success) |
| Content-Type | text/gemini; charset=utf-8; lang=en-US |