Skip to content

fix(release-drafter): add version templates and resolver#407

Merged
0x46616c6b merged 3 commits intomainfrom
fix/release-drafter-version-templates
May 5, 2026
Merged

fix(release-drafter): add version templates and resolver#407
0x46616c6b merged 3 commits intomainfrom
fix/release-drafter-version-templates

Conversation

@0x46616c6b
Copy link
Copy Markdown
Contributor

Type of Change

  • Bugfix
  • Enhancement / new feature
  • Refactoring
  • Documentation

Description

After #406 switched the release workflow from a tag-push (with explicit publish: true, name: ${{ github.ref_name }}, tag: ${{ github.ref_name }} inputs) to a continuous draft model triggered on push: main, release-drafter is now responsible for computing the next version itself. The config in .github/release-drafter.yml was missing name-template, tag-template, and version-resolver, so the latest run produced an empty draft (untagged-a75edd174a086d69cb7d) without title or tag, breaking the established vX.Y.Z naming scheme of all prior releases up to v2.7.0.

This PR restores the previous naming scheme by adding:

  • name-template / tag-template rendering as v$RESOLVED_VERSION
  • a version-resolver mapping the labels already consumed by the categories section to semver bumps (feature/enhancement → minor, fix/bugfix/bug/chore/dependencies/documentation → patch, breaking → major), with default: patch

The Dependabot major label is intentionally not part of the resolver: in PR labels it indicates the dependency's bump level, not a major release of this action. Real major bumps are reserved for the manually applied breaking label.

With these settings, the next draft will be calculated as v2.7.1 based on the currently merged fix:/chore:/dependency PRs since v2.7.0.

Checklist

  • Write tests
  • Make sure all tests pass
  • Update documentation
  • Review the Contributing Guideline and sign CLA
  • Reference relevant issue(s) and close them after merging

Follow-up

The existing empty draft (untagged-a75edd174a086d69cb7d) will not be reused by release-drafter and should be deleted manually so the next workflow run can create a fresh, correctly named draft.


The changes and the PR were generated by Claude.

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 <claude@anthropic.com>
@0x46616c6b 0x46616c6b marked this pull request as ready for review May 5, 2026 08:43
@0x46616c6b 0x46616c6b requested a review from a team as a code owner May 5, 2026 08:43
@0x46616c6b 0x46616c6b requested review from flaxel and soemo May 5, 2026 08:43
Comment thread .github/release-drafter.yml Outdated
Comment thread .github/release-drafter.yml
0x46616c6b and others added 2 commits May 5, 2026 10:56
Co-authored-by: Falk Puschner <falk.puschner@staffbase.com>
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 <claude@anthropic.com>
@0x46616c6b 0x46616c6b merged commit df0bb13 into main May 5, 2026
11 checks passed
@0x46616c6b 0x46616c6b deleted the fix/release-drafter-version-templates branch May 5, 2026 09:00
@github-actions github-actions Bot locked and limited conversation to collaborators May 5, 2026
@0x46616c6b 0x46616c6b added the chore Pull requests that are chores label May 5, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

chore Pull requests that are chores

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants