start-release

To create a git-flow release branch and bump the version automatically, you can run a command that initiates the branch via the git-flow-next CLI, updates version references in project files, commits the change with a conventional message, and pushes the branch to origin.

The best way to update version references across multiple project files for a release is to automate the process during release branch creation, which targets files like package.json, Cargo.toml, and VERSION to ensure all version references are consistently bumped and committed.

Yes, you need the git-flow-next CLI installed to start a release branch with this workflow, as the process enforces a workflow requiring the git-flow-next CLI to standardize branch creation, update version references, and push the release branch.

Yes, you can use this release branch workflow for projects with a Cargo.toml file, as the version bump automation specifically targets and updates version references across project files including package.json, Cargo.toml, and VERSION.

To commit and push a version bump to a new release branch in one step, you can execute a single command that creates the branch, updates the version, commits the change with a conventional message, and pushes the new release branch to the remote origin.