Deploying to gh-pages from @ e0de830 🚀

Author: woile

commands/version/index.html

@@ -2111,14 +2111,25 @@ <h2 id="components-and-next-version">Components and next version<a class="header
 <ul>
 <li><strong><code>--major</code></strong>, <strong><code>--minor</code></strong>, <strong><code>--patch</code></strong>: print only that component of the (possibly manual) project version. Requires <code>--project</code>, <code>--verbose</code>, or a manual version.</li>
 <li><strong><code>--next</code> <code>[MAJOR|MINOR|PATCH|NONE]</code></strong>: print the version after applying that bump to the current project or manual version. <code>NONE</code> leaves the version unchanged.</li>
+<li><strong><code>--next USE_GIT_COMMITS</code></strong>: derive the bump automatically from the commits since the tag matching the current version, using your commit rules' bump map (the same logic as <code>cz bump</code>). Passing <code>--next</code> with no value defaults to <code>USE_GIT_COMMITS</code>. If no tag matches the current version, all commits are considered. When there are no new commits (and the current version is not a pre-release), the command errors out. The functionality does not yet include advanced versioning like prereleases or exact_increment.</li>
 <li><strong><code>--tag</code></strong>: print the version formatted with your <code>tag_format</code> (requires <code>--project</code> or <code>--verbose</code>).</li>
 </ul>
-<p><code>--next USE_GIT_COMMITS</code> is reserved for a future feature (derive the bump from git history) and is not implemented yet.</p>
 <h2 id="examples">Examples<a class="headerlink" href="#examples" title="Permanent link">&para;</a></h2>
 <div class="highlight"><pre><span></span><code>cz<span class="w"> </span>version<span class="w"> </span>--project
 cz<span class="w"> </span>version<span class="w"> </span><span class="m">2</span>.0.0<span class="w"> </span>--next<span class="w"> </span>MAJOR
 cz<span class="w"> </span>version<span class="w"> </span>--project<span class="w"> </span>--major
 cz<span class="w"> </span>version<span class="w"> </span>--verbose
+
+<span class="c1"># Derive the next version from the commits since the current version&#39;s tag</span>
+cz<span class="w"> </span>version<span class="w"> </span>--project<span class="w"> </span>--next<span class="w"> </span>USE_GIT_COMMITS
+<span class="c1"># Equivalent shorthand (--next defaults to USE_GIT_COMMITS)</span>
+cz<span class="w"> </span>version<span class="w"> </span>--project<span class="w"> </span>--next
+<span class="c1"># Retrieve just the next major part of the version</span>
+cz<span class="w"> </span>version<span class="w"> </span>--project<span class="w"> </span>--next<span class="w"> </span>--major
+<span class="c1"># Works with a manual version too</span>
+cz<span class="w"> </span>version<span class="w"> </span><span class="m">1</span>.4.0<span class="w"> </span>--next
+<span class="c1"># Combine with --tag to format the derived version using your tag_format</span>
+cz<span class="w"> </span>version<span class="w"> </span>--project<span class="w"> </span>--next<span class="w"> </span>--tag
 </code></pre></div>
 
 
@@ -2140,7 +2151,7 @@ <h2 id="examples">Examples<a class="headerlink" href="#examples" title="Permanen
     <span class="md-icon" title="Last update">
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1zM12.5 7v5.2l4 2.4-1 1L11 13V7zM11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2z"/></svg>
     </span>
-    <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date" title="May 3, 2026 07:01:17 UTC">May 3, 2026</span>
+    <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date" title="July 24, 2026 10:22:15 UTC">July 24, 2026</span>
   </span>
 
 

commands/version/index.md

@@ -11,15 +11,25 @@ Get the version of the installed Commitizen or the current project (default: ins
 
 - **`--major`**, **`--minor`**, **`--patch`**: print only that component of the (possibly manual) project version. Requires `--project`, `--verbose`, or a manual version.
 - **`--next` `[MAJOR|MINOR|PATCH|NONE]`**: print the version after applying that bump to the current project or manual version. `NONE` leaves the version unchanged.
+- **`--next USE_GIT_COMMITS`**: derive the bump automatically from the commits since the tag matching the current version, using your commit rules' bump map (the same logic as `cz bump`). Passing `--next` with no value defaults to `USE_GIT_COMMITS`. If no tag matches the current version, all commits are considered. When there are no new commits (and the current version is not a pre-release), the command errors out. The functionality does not yet include advanced versioning like prereleases or exact_increment.
 - **`--tag`**: print the version formatted with your `tag_format` (requires `--project` or `--verbose`).
 
-`--next USE_GIT_COMMITS` is reserved for a future feature (derive the bump from git history) and is not implemented yet.
-
 ## Examples
 
 ```
 cz version --project
 cz version 2.0.0 --next MAJOR
 cz version --project --major
 cz version --verbose
+
+# Derive the next version from the commits since the current version's tag
+cz version --project --next USE_GIT_COMMITS
+# Equivalent shorthand (--next defaults to USE_GIT_COMMITS)
+cz version --project --next
+# Retrieve just the next major part of the version
+cz version --project --next --major
+# Works with a manual version too
+cz version 1.4.0 --next
+# Combine with --tag to format the derived version using your tag_format
+cz version --project --next --tag
 ```