From 44f10a078ef202228e22987bc4490d6d44d405f7 Mon Sep 17 00:00:00 2001 From: laughingman7743 Date: Sat, 17 Oct 2026 00:34:01 +0900 Subject: [PATCH] Keep 3.x releases from becoming the latest GitHub release The release step let GitHub mark the newest release as the latest, so v3.40.0, published after v4.1.0, replaced it as the repository's latest release until it was reset by hand. A release from this maintenance branch now passes make_latest: false. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/release.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml index 54f2e3e11..297a16a5b 100644 --- a/.github/workflows/release.yaml +++ b/.github/workflows/release.yaml @@ -48,3 +48,5 @@ jobs: dist/*.whl dist/*.tar.gz generate_release_notes: true + # A release of this maintenance line does not replace the latest release of master. + make_latest: false