diff --git a/.github/release-drafter.yml b/.github/release-drafter.yml
index def05cf7..6f1dde20 100644
--- a/.github/release-drafter.yml
+++ b/.github/release-drafter.yml
@@ -1,3 +1,21 @@
+name-template: 'v$RESOLVED_VERSION'
+tag-template: 'v$RESOLVED_VERSION'
+version-resolver:
+  major:
+    labels:
+      - 'breaking'
+  minor:
+    labels:
+      - 'feature'
+      - 'enhancement'
+  patch:
+    labels:
+      - 'fix'
+      - 'bug'
+      - 'chore'
+      - 'dependencies'
+      - 'documentation'
+  default: patch
 categories:
   - title: '🚀 Features'
     labels:
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