How One Startup Uses Semantic Versioning to Avoid Dependency Hell

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

How One Startup Uses Semantic Versioning to Avoid Dependency Hell

Listen for free

View show details

Lucas and Luna dive into how one startup uses semantic versioning (SemVer) to manage dependencies across 150 microservices without breaking production. They walk through the specific strategy: MAJOR.MINOR.PATCH tags on every npm package, automated pre-release validation, and a bot that blocks incompatible upgrades. The episode centers on the real numbers: before SemVer, the team faced 12 production incidents per quarter from version mismatches; after adopting a strict SemVer pipeline with lockfiles and canary deploys, that dropped to zero incidents for seven consecutive quarters. Lucas explains the trade-offs: the overhead of bumping versions versus the cost of unexpected breakage. Luna pushes back on whether SemVer is still relevant in a world of monorepos and trunk-based development. The discussion lands on a pragmatic middle ground — use SemVer for external-facing packages, and internal coherency for private modules. #SemanticVersioning #SemVer #DependencyManagement #Microservices #StartupEngineering #DevOps #PackageManagement #Versioning #ContinuousIntegration #Nodejs #Npm #BreakingChanges #Monorepo #SoftwareEngineering #TechStartup #BusinessAndTechnology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

No reviews yet