Release / Release Configuration based on Branch?

[ekristen]

Lets say for example the primary release branch is main and it's tagged a 2.1.0 but you have a release/1.x (at 1.5.1) for putting any hotfixes or back ports into.

Is there a way to have release-drafter automatically tag/release changes made to main on the 2.1.0 semver path and then have any merges into release/1.x trigger the next semver on the 1.5.1 path?

[jetersen]

Check the README.

We have commitish and filter-by-commitish and commitish can be applied via github action:

release-drafter/action.yml

Lines 41 to 45 in 569eb7e

	commitish:
	description: |
	The object that the release should be created to point to.
	required: false
	default: ''

[ekristen]

That is not what just happened. I set commitish to release/1.x and the filter setting to true and it created a tag on 2.x instead of 1.x

[ekristen]

Fetching parent commits of refs/heads/release/1.x since 2023-02-16T14:55:10Z -- the last tag was on 11/3/2022, could that be why? It's not looking far enough back?

Thu Nov 3 11:20:48 2022 -0400 fbacb2d (HEAD -> release/1.x, tag: 0.2.43, origin/release/1.x,) Merge pull request ...

[ekristen]

I've tried a few different things, even when this runs on the release/1.x it ultimately creates a change log off the default branch instead of the release/1.x branch. I'm using the github action.

name: auto-release

on:
  push:
    branches:
      - main
      - "release/*"

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
      - uses: release-drafter/release-drafter@v5
        with:
          publish: true
          prerelease: false
          config-name: auto-release.yml
        env:
          GITHUB_TOKEN: ${{ token }}

commitish: release/1.x
filter-by-commitish: true

name-template: "v$RESOLVED_VERSION"
tag-template: "$RESOLVED_VERSION"
version-template: "$MAJOR.$MINOR.$PATCH"

[jetersen]

It reads the config from the default branch so you cannot push the commitish into the config file. You need to supply it from github actions with block.

using:

with:
  ...
  commitish: ${{ github.ref }}

[ekristen]

ah interesting, well I'm getting closer.

After much much testing, it looks like there's some big differences from using git tag vs tagging via github UI or API.

For whatever reason when you tag using the CLI on say branch release/1.x and push the tag, the target_commitish from github gets set to primary branch

Additionally if you tag using the browser, the target commitish gets set to like release/1.x but with draft releaser the target commitish gets set to refs/heads/release/1.x

[ekristen]

The answer is the following:

The primary branch must have filter-by-commitish: true in the configuration, as this is not available on the action values.

Then the action must have the following set.

with:
  ...
  commitish: ${{ github.ref }}

Additionally if you were on main and then create release/1.x or release/2.x you will need to use GitHub UI or API to create a new tag and release on the new branch, otherwise release drafter will fail to find a previous tag and error out.