I used to think versioning was mostly about keeping old code alive.
Vanar made me think more about keeping old expectations alive.
In a lot of systems, a new version doesn’t just add features—it quietly changes how things feel. Timing shifts. Edge cases move. Things that used to be safe become “probably fine.” That’s when teams start pinning versions and avoiding upgrades, not because they hate progress, but because they hate surprises.
What’s interesting about Vanar’s approach is how stable those expectations seem to stay. When upgrades don’t rewrite the rules of the road, people stop treating them like risks and start treating them like maintenance.
And infrastructure that turns upgrades into maintenance usually ends up being trusted a lot longer.
