Node.js Versions - How Do They Work?
summary
Node.js uses a six‑month release cadence with even releases go to LTS and odd releases deprecated, LTS lasts 30 months split into 18 months active backporting and 12 months maintenance; commits land on master then teams cherry‑pick from master onto 0.x/4.x/6.x staging branches using git-based workflows and labels. Backports exclude most semver‑major changes, Branch Diff and changelog scripts automate audits, and Canary and the gold mine run tests against the top ~70 npm modules to catch regressions before release.
AI-written summary · about
chapters (11)
- 0:00Intro
- 5:54Nodejs Version History
- 8:43Nodejs Release Schedule
- 15:51Nodejs Release Branches
- 17:01Demo
- 22:07Branching
- 25:06Branch Diff
- 26:50Release Tools
- 27:34Breaking Changes
- 28:59Failures
- 30:57Conclusion
related talks
30mThe Life and Times of a Node.js Release
29mNode.js: The New and the Experimental
27mState of Node.js Core
27mNode.js 12: A Decade of Node.js
40mResponsible Use of Node.js & Open Source Software Utilizing Best Practices at an...
29mHow Did We Get Here
34mNode.js - What's Next - Catalyzing Change in the Node.js Ecosystem
24mNode.js 12: A decade of Node.js
