Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions .github/release-drafter.yml
Comment thread
0x46616c6b marked this conversation as resolved.
Original file line number Diff line number Diff line change
@@ -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:
Expand Down
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading