only use release drafter for minor releases (skip patch releases, and not clobber)

[tobybellwood]

Is there a way to configure release drafter to only create release notes for minor releases? We've been steadily building a 1.3.0 release from PRs, after our v1.2.0 release last month. Unfortunately, we had to release a patch v1.2.1 release last week, and release drafter has now recalculated our release notes since 1.2.1 and clobbered the notes that were already there (noting that 1.2.1 was branched from 1.2.0, and doesn't include the majority of the 1.3.0 changes).

Niche case I know, but is there a way to configure the release to build from a variable (e.g. LAST_MINOR_RELEASE)?

[TimonVS]

Unfortunately Release Drafter doesn't support this. Something like this has been requested in several other issues: #175, #404 and #203.

There's an open PR by @pdcmoreira which you can check out: #359. You can test the PR by changing your Release Drafter workflow file like so:

name: Release Drafter

on:
  push:
    # branches to consider in the event; optional, defaults to all
    branches:
      - master

jobs:
  update_release_draft:
    runs-on: ubuntu-latest
    steps:
      # Drafts your next Release notes as Pull Requests are merged into "master"
-     - uses: release-drafter/release-drafter@v5
+     - uses: pdcmoreira/release-drafter@branch-scoped
        with:
          # (Optional) specify config name to use, relative to .github/. Default: release-drafter.yml
          # config-name: my-config.yml
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Would that solve your problem?

[mkurz]

@tobybellwood I think you can solve this with the filter-by-commitish config. I wrote a little guide how to make things work, specially how to see and update the target_commitish value of a GitHub release (found at the end of my post): #656 (comment)

[mkurz]

A possible solution for this problem can be found here: #1061