From 51337b7fcdf6de1fec0b2ab9ffe39625022d636b Mon Sep 17 00:00:00 2001 From: Falk Scheerschmidt Date: Tue, 5 May 2026 10:42:15 +0200 Subject: [PATCH 1/3] fix(release-drafter): add version templates and resolver After commit 8465bc2 the workflow stopped passing tag/name inputs and expects release-drafter to compute the next version from the config. The config had no name-template, tag-template, or version-resolver, so drafts were created without a title or tag (e.g. untagged-a75edd17...). Add name-template/tag-template in the existing 'vX.Y.Z' scheme and a version-resolver that maps the labels already used by the categories section to semver bumps. The 'major' label is intentionally not part of the resolver because Dependabot uses it for the dependency's bump level, which should not promote this action to a major release. A dedicated 'breaking' label is reserved as an explicit opt-in for major bumps. Co-Authored-By: Claude --- .github/release-drafter.yml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/.github/release-drafter.yml b/.github/release-drafter.yml index def05cf7..8f6daaa5 100644 --- a/.github/release-drafter.yml +++ b/.github/release-drafter.yml @@ -1,3 +1,22 @@ +name-template: 'v$RESOLVED_VERSION' +tag-template: 'v$RESOLVED_VERSION' +version-resolver: + major: + labels: + - 'breaking' + minor: + labels: + - 'feature' + - 'enhancement' + patch: + labels: + - 'fix' + - 'bugfix' + - 'bug' + - 'chore' + - 'dependencies' + - 'documentation' + default: patch categories: - title: '🚀 Features' labels: From c937a2358fcae1137bdeded894a9a0dfbacea752 Mon Sep 17 00:00:00 2001 From: 0x46616c6b <0x46616c6b@users.noreply.github.com> Date: Tue, 5 May 2026 10:56:49 +0200 Subject: [PATCH 2/3] Update .github/release-drafter.yml Co-authored-by: Falk Puschner --- .github/release-drafter.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/release-drafter.yml b/.github/release-drafter.yml index 8f6daaa5..6f1dde20 100644 --- a/.github/release-drafter.yml +++ b/.github/release-drafter.yml @@ -11,7 +11,6 @@ version-resolver: patch: labels: - 'fix' - - 'bugfix' - 'bug' - 'chore' - 'dependencies' From c98502b33cb2b4d8a73276cb87265f903c68b5ac Mon Sep 17 00:00:00 2001 From: Falk Scheerschmidt Date: Tue, 5 May 2026 10:59:17 +0200 Subject: [PATCH 3/3] docs: update Release section for continuous draft workflow The previous wording referred to the old tag-push flow. Describe the current process: Release Drafter maintains a draft on every push to main with the next version resolved from PR labels, and a human publishes from the Releases UI when ready. Co-Authored-By: Claude --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 83165e30..d27842bf 100644 --- a/README.md +++ b/README.md @@ -90,7 +90,9 @@ Add a status label if the merge was successful or failed. # Release -You can create a new release by creating a new tag and bump the version in `package.json.` +Releases are maintained continuously by [Release Drafter](https://github.com/release-drafter/release-drafter). On every push to `main`, the open draft on the [Releases page](https://github.com/Staffbase/autodev-action/releases) is rebuilt from merged pull requests, with the next version (`vX.Y.Z`) resolved from PR labels (see `.github/release-drafter.yml` for the mapping). + +When the draft is ready to ship, open it on the Releases page and click **Publish release**. The tag is created at publish time. Remember to bump the `version` field in `package.json` in a follow-up PR so it matches the published tag. # Development