chore: migrate release drafter config to new schema - #166
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
soemo
approved these changes
Sep 30, 2026
flaxel
approved these changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal: remove the deprecation warnings Release Drafter prints on every run on
main.What changed
labelsmoved intowhen.labels.version-resolver.major/minor/patch.labelsbecame categories withtype: version-resolverandsemver-increment.version-resolver.default: patchstays.Label-to-version mapping is unchanged. Migration guide: release-drafter/release-drafter#1558
How to review
Check the label mapping against the old config. After merge, confirm the next Release Drafter run on
mainhas no deprecation warnings and still drafts the release.🤖 Generated with Claude Code