bazel-contrib/rules_python
Ver no GitHubCreate a program to handle release chores
Open
#2.790 aberto em 19 de abr. de 2025
Good first issuecleanuptype: process
Métricas do repositório
- Stars
- (679 stars)
- Métricas de merge de PR
- (Métricas PR pendentes)
Description
There's a few tedious and mechanical steps for our release process around replacing strings and updating docs. See RELEASING.md for all the steps.
It should be relatively easy to create a program that does the various string processing. The basic logic it needs to do is:
- Update CHANGELOG.md
- Replace the "Unreleased" title with
[X.Y.Z] - YYYY-MM-DD - Replace
0.0.0with X.Y.Z - Replace
v0-0-0withvX-Y-Z - Caveat: don't modify the "unreleased template" that is commented out.
- Replace the "Unreleased" title with
- Replace
VERSION_NEXT_*markers- caveat: don't replace them in CONTRIBUTING.md, RELEASING.md, and
.*dirs (.githhub etc)
- caveat: don't replace them in CONTRIBUTING.md, RELEASING.md, and
Something more advanced could look at which VERSION_NEXT_{FEATURE,PATCH} markers exist to figure out the next semantic version, but that's just a nice to have.
Just being able to do tools/private/release.py 1.4.0 would be a big improvement over all the ad-hoc stuff we have to do today.