fix(changelog): Warn when custom release.yml lacks semver fields #720
Conversation
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
BYK
force-pushed
the
fix/warn-missing-semver-in-release-config
branch
from
6087839 to
02b30bd
Compare
Contributor
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨
Bug Fixes 🐛Changelog
Documentation 📚
🤖 This preview updates automatically when you update the PR. |
Contributor
|
BYK
force-pushed
the
fix/warn-missing-semver-in-release-config
branch
from
02b30bd to
6dea984
Compare
BYK
force-pushed
the
fix/warn-missing-semver-in-release-config
branch
from
6dea984 to
94033c3
Compare
BYK
force-pushed
the
fix/warn-missing-semver-in-release-config
branch
2 times, most recently
from
0f071a2 to
0ea420c
Compare
BYK
force-pushed
the
fix/warn-missing-semver-in-release-config
branch
from
0ea420c to
7396626
Compare
When a custom .github/release.yml is used without semver fields on categories, PRs appear in the changelog but don't contribute to version bump detection. This causes the changelog preview to show "None" for semver impact. Changes: - Add warning when normalizing custom configs with missing semver fields - Update docs to clarify semver field requirement for version detection - Add tests for the warning behavior Fixes getsentry/sentry-wizard#1191 investigation
BYK
force-pushed
the
fix/warn-missing-semver-in-release-config
branch
from
7396626 to
595e180
Compare
betegon
approved these changes
Jan 15, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
.github/release.ymlhas categories withoutsemverfieldssemveris required for version bump detectionBackground
When investigating getsentry/sentry-wizard#1191, the changelog preview showed "None" for semver impact despite the PR having a
feat:prefix. The root cause was that sentry-wizard's custom.github/release.ymldefined categories withlabelsandcommit_patternsbut nosemverfields.Without
semverfields, PRs are correctly categorized in the changelog but don't contribute to version bump detection.Changes
Warning
When Craft normalizes a custom release config, it now warns about categories missing
semver:The warning:
Documentation
configuration.mdexplainingsemverrequirementgithub-actions.mdabout version bump detection requirementsRelated