diff --git a/Makefile b/Makefile
index 5e1d113d1..f746cdd2d 100644
--- a/Makefile
+++ b/Makefile
@@ -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)
diff --git a/doc/MAKING-RELEASES.md b/doc/MAKING-RELEASES.md
index 519c64d4d..d9f4fe670 100644
--- a/doc/MAKING-RELEASES.md
+++ b/doc/MAKING-RELEASES.md
@@ -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