chore: add semver field to release.yml categories for craft auto-versioning#5257
Open
jamescrosswell wants to merge 1 commit into
Open
chore: add semver field to release.yml categories for craft auto-versioning#5257jamescrosswell wants to merge 1 commit into
jamescrosswell wants to merge 1 commit into
Conversation
Craft's auto-versioning policy requires each changelog category to declare a `semver` field (major/minor/patch/none) so it can determine the bump type from commits since the last release. Without these fields, `craft prepare auto` fails with "none matched a category with a semver field". Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5257 +/- ##
==========================================
- Coverage 74.13% 74.12% -0.02%
==========================================
Files 508 508
Lines 18320 18320
Branches 3584 3584
==========================================
- Hits 13582 13580 -2
- Misses 3863 3864 +1
- Partials 875 876 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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 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.
Craft's
autoversioning policy needs each changelog category in.github/release.ymlto declare asemverfield (major/minor/patch/none). It uses that field to map commits since the last tag to a bump type and pick the next version.The current categories have no
semverfield, socraft prepare autofails with:See the recent failure: https://github.com/getsentry/sentry-dotnet/actions/runs/26375155007/job/77634036157
References
#skip-changelog