Makefile: add targets to upgrade pyln versions, push releases.

And use those in MAKING-RELEASES.md

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell 2022-08-24 19:59:17 +09:30 committed by Christian Decker
parent 3c80b22d6f
commit 0514269f48
2 changed files with 16 additions and 4 deletions

View file

@ -708,6 +708,20 @@ clean: obsclean
find . -name '*.nccout' -delete
if [ "${RUST}" -eq "1" ]; then cargo clean; fi
PYLNS=client proto testing
# See doc/MAKING-RELEASES.md
update-pyln-versions: $(PYLNS:%=update-pyln-version-%)
update-pyln-version-%:
@if [ -z "$(NEW_VERSION)" ]; then echo "Set NEW_VERSION!" >&2; exit 1; fi
cd contrib/pyln-$* && $(MAKE) upgrade-version
pyln-release: $(PYLNS:%=pyln-release-%)
pyln-release-%:
cd contrib/pyln-$* && $(MAKE) prod-release
# These must both be enabled for update-mocks
ifeq ($(DEVELOPER)$(EXPERIMENTAL_FEATURES),11)
update-mocks: $(ALL_TEST_PROGRAMS:%=update-mocks/%.c)

View file

@ -30,8 +30,7 @@ Here's a checklist for the release process.
3. Create a new CHANGELOG.md heading to `v<VERSION>rc1`, and create a link at
the bottom. Note that you should exactly copy the date and name format from
a previous release, as the `build-release.sh` script relies on this.
4. Update the contrib/pyln package __version__ strings, but do not upload
it to pypi!
4. Update the contrib/pyln package versions: `make update-pyln-versions NEW_VERSION=<VERSION>`
5. Create a PR with the above.
### Releasing -rc1
@ -78,8 +77,7 @@ Here's a checklist for the release process.
10. Append the signatures into a file called `SHA256SUMS.asc`, verify
with `gpg --verify SHA256SUMS.asc` and include the file in the draft
release.
11. In each contrib/pyln-* directory, `make test-release` and if that succeeds,
`make prod-release` to upload to pypi.org.
11.`make pyln-release` to upload pyln modules to pypi.org.
### Performing the Release