Yarn Version [hot] -

Yarn Version [hot] -

| Command / Option | Description | | :--- | :--- | | yarn version | Interactive prompt to select the new version (patch, minor, major, or custom). | | yarn version --new-version <version> | Bump to a specific version (e.g., yarn version --new-version 2.0.0 ). | | yarn version --major | Bump the major version (e.g., 1.2.3 → 2.0.0). | | yarn version --minor | Bump the minor version (e.g., 1.2.3 → 1.3.0). | | yarn version --patch | Bump the patch version (e.g., 1.2.3 → 1.2.4). | | --no-git-tag-version | Skip creating the Git tag and commit (only updates package.json ). | | --message "<message>" | Customize the Git commit message (e.g., --message "chore: release v%s" ). The %s is replaced with the new version. |

| Feature | yarn version | npm version | | :--- | :--- | :--- | | Git tag format | v1.0.0 (fixed) | v1.0.0 (default, configurable) | | Pre-commit hook | None (requires clean git state) | Supports preversion , version , postversion scripts | | Custom commit message | --message flag | --message flag | yarn version

Use yarn version for simple, automated version bumping in CI or release scripts. For complex monorepos or modern Yarn (v2+), prefer the workflow. Always push tags manually after verifying the release. Report generated based on Yarn Classic (v1.x) behavior. | Command / Option | Description | |

1. Overview

The yarn version command is a built-in Yarn (Classic) CLI command used to manage a project's version number. It automates the process of updating the version field in the package.json file, creating a corresponding Git tag, and optionally committing the change. | | yarn version --minor | Bump the minor version (e