We fail to follow SemVer and why it needn't matter

on YouTube ↗39m

" summary

Claim: the npm ecosystem already numbers 148,000 packages with over 80% under 1.0.0, so humans routinely break SemVer. Evidence: repository analysis and concrete examples of mislabeled releases and missing changelogs. Tools: automated use of Angular commit message conventions, generated changelogs, CI (Travis) and a release bot called semantic-release that runs old tests to perform breaking change detection and only publishes properly declared major/minor/patch releases. The thing built is an automated release pipeline that prevents undeclared breaking releases.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 3:32Semantic Versioning
3. 5:07Version Ranges
4. 10:32Commit Message Conventions
5. 37:50Coffee Break

" related talks

• 29mBreaking ChangesJames Coglan · JSConf EU 2018
• 41mBreaking ChangesJames Coglan · Øredev 2019
• 39mManaging an Open Source ProjectKent C. Dodds · All Things Open 2019
• 37mNode.js Package Maintenance...Bethany Griggs, Glenn Hinks, Darcy Clark, Dominykas Blyze, Rodion Abdurakhimov · OpenJS World 2021
• 30mHappy Developers, Healthy Modules - Together We Can Do ThisMichael Dawson · Node+JS Interactive 2019
• 41mHow the npm CLI Team Manages (Almost) 100 Open Source ProjectsLuke Karrys · OpenJS World 2023
• 16mDependency Hell Just Froze OverStephan Bönnemann · NodeConfEU 2015
• 33mNode.js Versions - How Do They Work?Myles Borins · JSConf.Asia 2016