How Web APIs Use Semantic Versioning at Scale

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 Web APIs Use Semantic Versioning at Scale

Listen for free

View show details

Episode 77 of The API Podcast with Fexingo dives into semantic versioning for web APIs—how version numbers like 2.1.3 communicate breaking changes, new features, and patches. Lucas and Luna explore real-world cases from Stripe, GitHub, and the Node.js ecosystem, and unpack why 'semver' became the de facto standard for API contracts. They discuss the tension between strict semver and pragmatic pre-1.0 approaches, and how tools like npm and package-lock.json enforce version ranges. If you've ever wondered whether a minor bump can break your integration, or why some APIs stay at 1.x for years, this episode explains the discipline behind the numbers. #SemanticVersioning #APIVersioning #Stripe #GitHub #NodeJS #npm #Semver #BreakingChanges #APICompatibility #VersionRanges #CaretVersions #TildeVersions #PackageLock #BackwardCompatibility #Technology #WebAPIs #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

No reviews yet