Repository navigation
ci(release): base the draft on releases from the same branch - #1609
Closed
dimitri-yatsenko wants to merge 1 commit into
Closed
dimitri-yatsenko wants to merge 1 commit into
dimitri-yatsenko wants to merge 1 commit into
Conversation
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.
dimitri-yatsenko
requested review from
MilagrosMarin,
lum-agilyti and
ttngu207
October 17, 2026 22:03
Member
Author
|
Superseded by #1588: releases are now cut from annotated tags whose messages are the notes, and release-drafter is removed, so its baseline no longer matters. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.