Repository navigation
ci(release): Update .craft.yml for craft 3.9.0 - #729
Open
sentry-junior[bot] wants to merge 1 commit into
Open
sentry-junior[bot] wants to merge 1 commit into
sentry-junior[bot] wants to merge 1 commit into
Conversation
Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8c2ee4d. Configure here.
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.

Follow-up to #728, which moved the release workflow to
getsentry/craft@v3(currently 3.9.0). This sets.craft.ymlminVersionto "3.9.0" (was "2.21.4").The other defaults craft picks from
minVersion(auto-bump from 2.21.0,autoversioning from 2.14.0) already apply at 2.21.4, so release behavior doesn't change.preReleaseCommand: ""andversioning.policy: calverstay as they are.craft 3.9.0
prepare 99.0.0 --dry-run --no-push, run before and after this change, gives the same result: it bumps only CHANGELOG.md with no new errors or warnings.via @BYK.
--
View Session in Sentry