Repository navigation
meta(cli): Use Craft's built-in post-release version bump - #1796
Merged
Merged
Conversation
Craft 3.7.0 can bump to the next development version after a release (postReleaseBump), so the hand-written post-release script is no longer needed. Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
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 aa81e86. Configure here.
BYK
approved these changes
Nov 2, 2026
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.
Craft 3.7.0 can set the next development version itself after a release (
postReleaseBump). This replacesbump-version.ts --postfor thepackages/cliworkspace.postReleaseBump: truegives the same version asnpm version preminor --preid=dev(0.48.0→0.49.0-dev.0). Craft writes it with the existing--precommand, then commitsmeta: Bump new development versionwith#skip-changelog, pulls, and pushes.--prewrites the dev version, it also syncs the tracked skill frontmatter (Keep generated CLI skill versions in sync after releases #1415 added that to--postonly). As a result, release commits now also set the skill files to the release version. Before, they kept the dev version.--postmode and its git handling are removed. The regression test now covers--pre.minVersiongoes to3.7.0.prepareusesgetsentry/craft@v3, which is 3.7.0 now.I checked the resolved config against Craft 3.7.0's schema. The bump-version test passes, I ran the script on the real tree (47 files updated), and oxlint/oxfmt are clean.
via @BYK.
--
View Session in Sentry