A reliable developmentrelease workflow for open source Python libraries
Talkat PythonAsia 2026 · on Sunday, 2026-03-22· at 11:15· Yuchengco Hall 4th Flr. Y409 (Workshop Room 2)·
summary
Case study of a Python library with 100+ PyPI releases shows a CI/CD workflow that actually works: build once and reuse the artifact, trigger publishes from git tags, and let hatchvcs embed the tag-derived version in wheels. Uses scribe for committed markdown fragments plus a small Python script to map fragment categories to patch/minor/major bumps, a GitHub Actions pipeline that opens release PRs and then tags on merge, and preview wheels for PRs. Key patterns: depotent builds and change log fragments.
AI-written summary · about
chapters (9)
- 0:00Reliable Python workflows
- 3:21CI/CD release pipelines
- 5:28Automating changelogs and version bumps
- 15:12Conventional commits vs change sets
- 19:32Python versioning scripts
- 23:23End-to-end workflow demo
- 25:29Security in GitHub Actions
- 28:25Improving developer experience with preview wheels
- 29:52Key takeaways
related talks
01h 21mSecure Python Packaging & Release Using Continuous Deployment
39mA Pythonic Approach to Continuous Delivery
38mTools for Maintaining an Open Source Project
47mPublishing & Maintaining Opensource Python Packages in PyPI
32mLet's Deploy an Open Source Library
23mGitHub Actions & Python
49mHow to build Python-C++ libraries
26mOpen Source on Easy Mode