How to release open source library in 2020
summary
Shows a concrete workflow and a working tool: uses conventional commits to auto-calculate semver, creates a staging branch and PR, then CI runs a publish job; the three-step flow prepare / review / trigger removes the local blocking step and reduces human error. Demonstrates ship.js running on CircleCI (creates tags, npm publish, Slack notifications), proves it by releasing ship.js itself and small demo libraries, and reports end-to-end test times around four minutes.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:17Instant Search
- 5:05What about Releasing Apps
- 6:34Making Mistakes
- 9:55Things To Do When Releasing Libraries
- 10:41Conventional Commits
- 13:11Conventional Changelog
- 22:40Review the Pull Request
- 24:37Discussion Merge
- 28:21Part 3
- 33:05How Do You Integrate Shift Js into Your Library
- 42:20Update the Change Log
- 46:04Shift Js Config File
- 1:06:00Can I Configure this Tool To Publish in a Private Npm Registry
- 1:06:50Is There a Possibility To Change as a Registry Url
related talks
32mLet's Deploy an Open Source Library
31mRelease it like a pro!
25mReleasing at the speed of light
20mStreamlining Release Management for DevOps Success
48mRelease-plz: releasing crates like it's 2023
23mTake the Leap into Open Source Projects
30mBringing Continuous Delivery to Open Source
16mLightning Talk - Automating SemVer for Fun and Profit: ...