search

inventree / InvenTree

Open Source Inventory Management System
https://docs.inventree.org
MIT License
4.35k stars 790 forks source link

Automated release cycles #4623

Open SchrodingersGat opened 1 year ago

SchrodingersGat commented 1 year ago

Release cycle is now getting pretty complex, it is time to consolidate and automated the process (as much as possible). Following stages need to be considered:

### Things that could be automated
- [x] Automate workflow for back-porting bug fixes to stable branch
- [ ] Generate new release (automated release notes)
- [ ] Bump version number to next minor dev version (e.g. "0.12.0" -> "0.13.0 dev")
- [ ] Create new bugfix branch for new minor release
- [x] Create documentation release (better yet, move docs into this repo)
- [x] Python bindings release (optional, separate)
- [x] App release (optional, separate)
- [ ] Website blog post
- [ ] Social media updates (twitter / reddit)
matmair commented 1 year ago

Related https://github.com/inventree/inventree-docs/issues/375 We would probably need to split this into a manual workflow before a release and an action during the release.

SchrodingersGat commented 1 year ago

We should also spin the generation of API docs into this also

matmair commented 1 year ago

That would nicely close out https://github.com/inventree/InvenTree/issues/2493; although I think we should not pack too much into this issue as it will probably delay it

matmair commented 11 months ago

Might be intresting for automating releases and adding back a changelog https://github.com/googleapis/release-please https://github.com/googleapis/repo-automation-bots/tree/main/packages/release-trigger