Explores the meaning of zero-major versioning in software, challenges assumptions about production readiness, and discusses Semantic Versioning (SemVer) as a communication contract.
Introduces EffVer, a versioning scheme that communicates the expected effort required for users to upgrade, as an alternative to SemVer and CalVer.
Learn how to sort Git tags by semantic version using command-line options and global configuration settings.
Explains how to upgrade indirect npm dependencies, covering semantic versioning, caret/tilde ranges, and practical steps for security updates.
A guide to automatically setting Helm Chart version and appVersion properties using GitHub Actions CI/CD pipelines, ensuring Semantic Versioning compliance.
An analysis of semantic versioning (SemVer) and the practical challenges of maintaining true backwards compatibility in software APIs.
Critique of Semantic Versioning's practical limitations and why it can't guarantee API stability, using real-world examples like the cryptography package.
A guide to using MinVer for semantic versioning of NuGet packages based on Git tags, explaining version number components.
A guide to implementing API versioning in ASP.NET Core using Swashbuckle, covering routing, models, and Swagger configuration.
A developer's analysis of how a minor version update in a Composer dependency caused a breaking change in a Laravel project, highlighting versioning pitfalls.
Explains how to use Maven's new ${revision}, ${sha1}, and ${changelist} properties for simplified, centralized versioning in projects.
Explains Semantic Versioning (SemVer), covering major, minor, and patch version numbers and their meaning for software releases.
Explains how to manage library dependencies using Maven's Bill of Materials (BOM) and semantic versioning for easier upgrades.
Explains npm's change from tilde (~) to caret (^) for '--save' and the semantic versioning implications for dependency updates.
Discusses the importance of proper software versioning, common bad practices, and the specific challenges in the .NET ecosystem.
A critique of modern software versioning practices, proposing clearer definitions for semantic versioning (x.y.z) and addressing confusion caused by terms like alpha, beta, and release candidates.
