Support a "Unreleased" pre-release

[cb80]

Hello @anton-yurchenko

Description

https://keepachangelog.com/ defines the Unreleased section. I propose to create/update/replace a pre-release whenever a specific tag is updated e.g. a latest tag? As a pre-release it is identified as non-production ready. Also the latest tag is potentially moved with every merge to the main branch.

The benefit from my point of view is that you can automatically deliver something users can test with.

This is how it could be used:

on:
  push:
    tags:
    - 'latest'

...

    - name: Latest Release
      uses: docker://antonyurchenko/git-release:latest
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        DRAFT_RELEASE: "false"
        PRE_RELEASE: "true"
        CHANGELOG_FILE: "CHANGELOG.md"
        CHANGELOG_SECTION: "Unreleased"
        ALLOW_EMPTY_CHANGELOG: "false"
      with:
        args: |
            build/*-amd64.zip

What do you think about that?

PS: From the docs: Note: The release event is not triggered for draft releases.

Reference

• https://keepachangelog.com/
• https://docs.github.com/en/actions/reference/events-that-trigger-workflows#release-event-release

[cb80]

I meanwhile created an action https://github.com/cb80/pubrel to get going. But I love your approach to use the changelog. Also mine cannot glob files, create a prerelease and other features. So please don't misunderstand that as "lost interest".

[anton-yurchenko]

Hello @cb80 😉
That is a great idea, which will certainly help some folks!

Right now, I am refactoring this action in an attempt to reduce the number of packages and simplify the code as a part of the upcoming v4.0.0. The recreation of the Unreleased GitHub release might be added as well, although I would like to tackle that after the refactor, possibly still as a part of the v4.

Please stay tuned in this issue

Thank you for your help 👑

[anton-yurchenko]

Unreleased support has been added in v4.1.0 🎉

Thank you!