I’m dropping GitVersion.

by Oct 30, 2024

I’m dropping GitVersion.

After working with GitVersion for a while, I decided to simplify things.

GitVersion is powerful, but it often felt like overkill for my projects. I wanted something that followed SemVer, didn’t require complex configuration, and “just worked” without any headaches.

MinVer fit the bill perfectly: a simple NuGet package that handles versioning directly from Git tags—no configuration needed. The default out-of-the-box configuration of MinVer is exactly what I want.

The only change I made was to not prefix Git tags with ‘v’. MinVer can handle this in its configuration, but I prefer to have zero-config.

The unique thing about MinVer is that it will auto-version your project by just adding it. You don’t need to do anything.

Because it handles auto-versioning, there’s no need to set up versioning in your build pipeline. Your build also becomes simpler.

Less configuration means fewer rules, fewer headaches, and more time to focus on what really matters.

Keeping it stupid simple!

Are you using GitVersion? Do you need the complexity?

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more