From f4638ca716090c9c9e798b6a10784ce67724c3db Mon Sep 17 00:00:00 2001 From: Dimitri Yatsenko Date: Sat, 17 Oct 2026 16:20:03 -0500 Subject: [PATCH] ci(release): base the draft on releases from the same branch Release-drafter takes the latest release on any branch as the baseline of the next draft. A release from a maintenance branch (v0.14.10 from maint/0.14, or a v2.3.x patch from maint/2.3) then becomes the baseline for master's draft, and master PRs merged before it drop out of the notes. filter-by-commitish limits the baseline to releases whose target is the branch the workflow runs on. Release-drafter strips refs/heads/ before comparing, so past releases that target either master or refs/heads/master both match. --- .github/release_drafter.yaml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/release_drafter.yaml b/.github/release_drafter.yaml index 412adf1ee..d2ecec30f 100644 --- a/.github/release_drafter.yaml +++ b/.github/release_drafter.yaml @@ -10,6 +10,10 @@ version-resolver: - 'documentation' - 'enhancement' - 'bug' +# Base each draft on the latest release cut from the same branch. Without this, +# a release from a maintenance branch (maint/0.14, maint/2.3) becomes the baseline +# for master's draft, and master PRs merged before it drop out of the notes. +filter-by-commitish: true name-template: '$RESOLVED_VERSION' tag-template: 'v$RESOLVED_VERSION' categories: