Help needed with publishing a release when pushed to master

[dreinon]

Hi!
My current workflow is merging different feat, fix, etc, PR's into develop and then, when I want to release a new version, opening and merging a PR from develop to master, which will deploy to production, bump project's version (npm) and make a github release, using semantic-version, which uses commit messages to generate the changelog.

I would like to use release drafter to be able to use PR names. I have the release drafter config set up, but have doubts on how to do all the release process when merging from develop to master. My idea is:

• PR merged into develop:
  • creates/updates draft release according to labels (btw, using autolabeler)
• PR merged from develop into master:
  • this PR doesn't get added to draft release (autolabeler marks PRs from develop branch as skip-changelog, which are excluded)
  • bump project's version (npm) and commit changes (*)
  • execute release drafter to publish draft release (*)

I have doubts on how to do the steps marked as (*). Since release-drafter is responsible to resolve the new version based on semver, but the github release should be published after the project's version is bumped in order to include the bump commit.

Thanks!

Release Drafter Config

name-template: 'v$RESOLVED_VERSION 🌈'

tag-template: 'v$RESOLVED_VERSION'

categories:
    - title: '🚀 Features'
      labels: 'feature'

    - title: '✨ Improvements'
      labels: 'improvement'

    - title: '🐎 Performance'
      labels: 'performance'

    - title: '🔨 Refactor'
      labels: 'refactor'

    - title: '🐛 Bug Fixes'
      labels: 'bug'

    - title: '🧰 Maintenance'
      label: 'chore'

change-template: '- $TITLE @$AUTHOR (#$NUMBER)'

change-title-escapes: '\<*_&'

version-resolver:
    major:
        labels:
            - 'major'

    minor:
        labels:
            - 'feature'
            - 'improvement'

    patch:
        labels:
            - 'chore'
            - 'fix'
            - 'performance'
            - 'refactor'

    default: patch
replacers:
    - search: '/(build|chore|ci|docs|feat|fix|improve|perf|refactor|revert|style|test)(\(\w+\)?((?=:\s)|(?=!:\s)))?(!)?(:)(\s.*)/g'
      replace: '$2$6'

autolabeler:
  - label: 'chore'
    title:
      - '/chore/i'

  - label: 'bug'
    title:
      - '/fix/i'

  - label: 'feature'
    title:
      - '/feat/i'

  - label: 'refactor'
    title:
      - '/refactor/i'

  - label: 'improvement'
    title:
      - '/improve/i'

  - label: 'refactor'
    title:
      - '/refactor/i'
  
template: |
    ## What's Changed

    $CHANGES

[dreinon]

Finally what I have done is:

• I have a PR Labeler action which labels PRs with release drafter. (If PRs come from develop, they are marked as skip-changelog, which is then ignored)

• When a PR from any branch to develop (already labeled according to its conventional-commit friendly title) is merged, release drafter is run and the draft release gets updated

• When we want to make a release, we create a PR from develop to main (marked as skip-changelog). On merged, we run release-drafter which doesn't update the releasee draft since this PR has an ignored label, but it outputs the tag_name, which from we get the version, and we do npm version <> -m "whatever %s [skip ci]", and then push, and push the tags (important, having done the checkout of the job with a custom personal token that has the workflows permissions).

• There's an action which triggers on push to a tag that runs release drafter with publish to true and with the version out of the name of the tag that triggered the workflow.

[ssbarnea]

I am quite interested to see some pipelines that are able to update a git tracked changelog when a release is going to happen. Likely these are supposed to be manually triggered actions that can produce pull requests with updated version and changelog.