💾 Archived View for d.moonfire.us › blog › 2021 › 08 › 29 › semantic-release-dotnet captured on 2023-04-19 at 23:32:38. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-01-29)
-=-=-=-=-=-=-
I've pretty much embraced[1] semantic-release[2] for most of my release processes, both for books and software. It has gone pretty smoothly, but occasionally I find myself hacking it to get something working. One of the more recent ones (and something that is going to affect me in the near future) is the interaction between semantic-release and .NET projects.
2: https://semantic-release.gitbook.io/semantic-release/
These are two very different systems, including packaging, and there are plenty of NuGet packages to do semantic-release as a .NET project, but I use Node for my package management, thanks to Husky[3]. So, after a year or so of writing up little ad-hoc programs, I decided to write a formal package.
3: https://typicode.github.io/husky/#/
Introducing semantic-release-dotnet[4]. It is basically a “prepare” plugin for `semantic-release` and writes out the `<Version/>` element into `Directory.Build.props` or a `.csproj` file. It uses minimatch (via glob) to update the files, so you can edit the project files directly and it will write out certain files if they are missing.
4: https://gitlab.com/dmoonfire/semantic-release-dotnet/
Categories:
Tags:
Below are various useful links within this site and to related sites (not all have been converted over to Gemini).
https://d.moonfire.us/blog/2021/08/29/semantic-release-dotnet/