fix: prerelease version increment should not bump base version

The create-tag workflow was always applying the bump type to the base
version, even when already on a prerelease channel. This caused
0.11.0-next.1 + minor + next to produce 0.12.0-next.1 instead of
0.11.0-next.2.

Fixed bump_version logic to handle three flows:
- Same prerelease channel: keep base, increment counter
- Promoting prerelease to stable: use base as-is
- Stable to new prerelease or stable bump: apply bump type

Also reverts manifests from 0.12.0-next.1 back to 0.11.0-next.1.

Author: ytallo

.github/workflows/create-tag.yml

@@ -112,13 +112,32 @@ jobs:
             local base="${current%%-*}"
             IFS='.' read -r major minor patch <<< "$base"
 
-            case "$bump_type" in
-              major) major=$((major + 1)); minor=0; patch=0 ;;
-              minor) minor=$((minor + 1)); patch=0 ;;
-              patch) patch=$((patch + 1)) ;;
-            esac
+            # Check if current version already has the requested pre-release label
+            local current_pre=""
+            if [[ "$current" =~ -([a-z]+)\.[0-9]+$ ]]; then
+              current_pre="${BASH_REMATCH[1]}"
+            fi
 
-            local new_base="${major}.${minor}.${patch}"
+            local new_base
+            if [[ "$PRERELEASE" != "none" && "$current_pre" == "$PRERELEASE" ]]; then
+              # Same pre-release channel: keep base, increment counter
+              # e.g. 0.12.0-next.1 → 0.12.0-next.2
+              new_base="$base"
+            elif [[ "$PRERELEASE" == "none" && -n "$current_pre" ]]; then
+              # Promoting pre-release to stable: use base as-is
+              # e.g. 0.12.0-next.3 → 0.12.0
+              new_base="$base"
+            else
+              # Stable → stable bump, or stable → new pre-release
+              # e.g. 0.11.0 + minor → 0.12.0
+              # e.g. 0.11.0 + minor + next → 0.12.0-next.1
+              case "$bump_type" in
+                major) major=$((major + 1)); minor=0; patch=0 ;;
+                minor) minor=$((minor + 1)); patch=0 ;;
+                patch) patch=$((patch + 1)) ;;
+              esac
+              new_base="${major}.${minor}.${patch}"
+            fi
 
             if [[ "$PRERELEASE" != "none" ]]; then
               local existing

console/packages/console-rust/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "iii-console"
-version = "0.12.0-next.1"
+version = "0.11.0-next.1"
 edition = "2021"
 description = "Developer console for the iii engine"
 license = "Apache-2.0"

engine/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "iii"
-version = "0.12.0-next.1"
+version = "0.11.0-next.1"
 edition = "2024"
 license = "Elastic-2.0"
 

sdk/packages/node/iii-browser/package.json

@@ -1,6 +1,6 @@
 {
   "name": "iii-browser-sdk",
-  "version": "0.12.0-next.1",
+  "version": "0.11.0-next.1",
   "private": false,
   "publishConfig": {
     "access": "public"

sdk/packages/node/iii/package.json

@@ -1,6 +1,6 @@
 {
   "name": "iii-sdk",
-  "version": "0.12.0-next.1",
+  "version": "0.11.0-next.1",
   "private": false,
   "publishConfig": {
     "access": "public"

sdk/packages/python/iii/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "iii-sdk"
-version = "0.12.0.dev1"
+version = "0.11.0.dev1"
 description = "III SDK for Python"
 authors = [{ name = "III" }]
 license = { text = "Apache-2.0" }

sdk/packages/rust/iii/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "iii-sdk"
-version = "0.12.0-next.1"
+version = "0.11.0-next.1"
 edition = "2024"
 rust-version = "1.85"
 license = "Apache-2.0"