Repository navigation
ci(release): Use Craft's default changelog categories - #2759
Merged
Merged
Conversation
Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
Contributor
|
10 screenshot changes — 10 changed · 0 added · 0 removed Review screenshots in Frameshift
Show 4 more changed screenshots
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
BYK
approved these changes
Nov 5, 2026
22 tasks done
This branch was successfully deployed
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.
Warning
Merge this only after a Craft 3.x release that includes getsentry/craft#962 is out. Until then, Craft's default categories make
bump=auto(the default) release 1.0.0 on the nexttype!:commit.This deletes
.github/release.yml, so Craft uses its default changelog categories. BYK asked for this on #2745: use the defaults and fix Craft instead of keeping a local override.The file was a copy of Craft's defaults with one difference: breaking changes were
semver: minor, soautocouldn't release 1.0.0 while Junior is 0.x. getsentry/craft#962 builds that rule into Craft. Below 1.0.0,autoandpretreat a breaking change as a minor bump, and only an explicitmajoror exact version releases 1.0.0. The release workflow uses the floatinggetsentry/craft@v3tag, so the fix reaches Junior as soon as Craft releases it.Nothing else referenced the file.
releasing.mdalready says breaking changes bump the minor version, and that stays true once the fix is released.Verification
pnpm release:checkand prettier pass.feat!:commit:auto→ 0.6.0,pre→ 0.6.0-alpha.0,major→ 1.0.0.auto→ 1.0.0. That's why this PR must wait.via @BYK.
--
View Session in Sentry