docs: update version references to v0.12.3

Author: fenio

README.md

@@ -144,7 +144,7 @@ The TNS CSI Driver is published to both Docker Hub and GitHub Container Registry
 #### Docker Hub (recommended)
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
@@ -159,7 +159,7 @@ helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
 **NVMe-oF Example:**
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
@@ -178,7 +178,7 @@ helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
 **iSCSI Example:**
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \

charts/tns-csi-driver/Chart.yaml

@@ -7,12 +7,12 @@ type: application
 
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
-version: 0.12.1
+version: 0.12.3
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
-appVersion: "v0.12.1"
+appVersion: "v0.12.3"
 
 keywords:
   - storage

docs/DEPLOYMENT.md

@@ -242,7 +242,7 @@ The easiest way to deploy the CSI driver is using the Helm chart from Docker Hub
 **For NFS:**
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
@@ -257,7 +257,7 @@ helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
 **For NVMe-oF:**
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
@@ -275,7 +275,7 @@ helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
 **For iSCSI:**
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
@@ -315,15 +315,15 @@ If you want to build your own image instead of using the published one:
 make build
 
 # Build Docker image
-docker build -t your-registry/tns-csi-driver:v0.12.1 .
+docker build -t your-registry/tns-csi-driver:v0.12.3 .
 
 # Push to your registry (DockerHub, GitHub Container Registry, etc.)
-docker push your-registry/tns-csi-driver:v0.12.1
+docker push your-registry/tns-csi-driver:v0.12.3
 ```
 
 If using a private registry, ensure your Kubernetes cluster has pull access.
 
-The published image is available at: `bfenski/tns-csi:v0.12.1`
+The published image is available at: `bfenski/tns-csi:v0.12.3`
 
 ## Step 3: Configure Deployment Manifests (Manual Deployment Only)
 
@@ -350,7 +350,7 @@ image: your-registry/tns-csi-driver:latest
 
 With:
 ```yaml
-image: your-registry/tns-csi-driver:v0.12.1
+image: your-registry/tns-csi-driver:v0.12.3
 ```
 
 ### 3.3 Update StorageClass
@@ -771,7 +771,7 @@ Volumes created with earlier versions will **not be recognized** by the new driv
 2. Upgrade the driver:
    ```bash
    helm upgrade tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-     --version 0.12.1 \
+     --version 0.12.3 \
      --namespace kube-system \
      --reuse-values
    ```

docs/FEATURES.md

@@ -1270,6 +1270,6 @@ helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
 ---
 
 **Last Updated**: 2026-01-29
-**Driver Version**: v0.12.1
+**Driver Version**: v0.12.3
 **Kubernetes Version Tested**: 1.27+
 **Go Version**: 1.26.0+

docs/KIND.md

@@ -38,7 +38,7 @@ docker exec truenas-csi-test-worker apt-get install -y nfs-common
 ```bash
 # Install from OCI registry
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
@@ -128,10 +128,10 @@ docker exec truenas-csi-test-worker apt-get install -y nfs-common
 
 ```bash
 # Build
-docker build -t bfenski/tns-csi:v0.12.1 .
+docker build -t bfenski/tns-csi:v0.12.3 .
 
 # Load into Kind
-kind load docker-image bfenski/tns-csi:v0.12.1 --name truenas-csi-test
+kind load docker-image bfenski/tns-csi:v0.12.3 --name truenas-csi-test
 ```
 
 ### 4. Create Kubernetes Secret

docs/QUICKSTART-ISCSI.md

@@ -96,7 +96,7 @@ That's it! Unlike NVMe-oF, iSCSI doesn't require pre-configured portals or targe
 
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
@@ -255,7 +255,7 @@ To keep volumes on TrueNAS when PVCs are deleted:
 
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
   --set truenas.apiKey="YOUR-API-KEY" \

docs/QUICKSTART.md

@@ -20,7 +20,7 @@ The fastest way to get started is using Helm from the OCI registry:
 
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
@@ -256,7 +256,7 @@ kubectl describe pvc <pvc-name>
 ### Enable Debug Logging
 ```bash
 helm upgrade tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --reuse-values \
   --set controller.extraArgs="{--v=5}" \
@@ -314,7 +314,7 @@ storageClasses:
 Install with values file:
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --values my-values.yaml
@@ -326,7 +326,7 @@ To keep volumes on TrueNAS even when PVCs are deleted (useful for data protectio
 
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
@@ -356,7 +356,7 @@ To use NVMe-oF instead of NFS:
 
 ```bash
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --create-namespace \
   --set truenas.url="wss://YOUR-TRUENAS-IP:443/api/current" \
@@ -426,7 +426,7 @@ To upgrade to a newer version:
 
 ```bash
 helm upgrade tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --namespace kube-system \
   --reuse-values
 ```

docs/VERSIONING.md

@@ -6,15 +6,15 @@ This document describes the versioning strategy for tns-csi.
 
 tns-csi follows [Semantic Versioning](https://semver.org/) (SemVer):
 
-- **MAJOR.MINOR.PATCH** (e.g., `v0.12.1`)
-- Tags are prefixed with `v` (e.g., `v0.12.1`, `v1.0.0`)
+- **MAJOR.MINOR.PATCH** (e.g., `v0.12.3`)
+- Tags are prefixed with `v` (e.g., `v0.12.3`, `v1.0.0`)
 
 ## Version Sources
 
 The version is determined at **build time** and embedded in the binary. The version comes from:
 
 1. **Git tags** (preferred) - When building from a tagged commit, the version is the tag name
-2. **Git describe** - For non-tagged commits, format is `v0.12.1-3-gabc1234` (3 commits after v0.12.1)
+2. **Git describe** - For non-tagged commits, format is `v0.12.3-3-gabc1234` (3 commits after v0.12.3)
 3. **"dev"** - Fallback when git is not available
 
 ## What's Embedded
@@ -23,7 +23,7 @@ Each build includes:
 
 | Field | Description | Example |
 |-------|-------------|---------|
-| Version | Semantic version from git tag | `v0.12.1` |
+| Version | Semantic version from git tag | `v0.12.3` |
 | Git Commit | Short SHA of the commit | `abc1234` |
 | Build Date | UTC timestamp of build | `2025-12-21T10:30:00Z` |
 | Go Version | Go compiler version | `go1.26.0` |
@@ -39,7 +39,7 @@ tns-csi-driver --show-version
 
 Output:
 ```
-tns.csi.io version: v0.12.1
+tns.csi.io version: v0.12.3
   Git commit: abc1234
   Build date: 2025-12-21T10:30:00Z
   Go version: go1.26.0
@@ -61,7 +61,7 @@ curl http://localhost:8080/version
 Response:
 ```json
 {
-  "version": "v0.12.1",
+  "version": "v0.12.3",
   "gitCommit": "abc1234",
   "buildDate": "2025-12-21T10:30:00Z",
   "goVersion": "go1.26.0",
@@ -73,7 +73,7 @@ Response:
 
 The version is logged at startup:
 ```
-Starting TNS CSI Driver v0.12.1 (commit: abc1234, built: 2025-12-21T10:30:00Z)
+Starting TNS CSI Driver v0.12.3 (commit: abc1234, built: 2025-12-21T10:30:00Z)
 ```
 
 ### From Helm
@@ -91,7 +91,7 @@ When a version is released, Docker images are tagged with:
 
 | Tag | Description | Stability |
 |-----|-------------|-----------|
-| `v0.12.1` | Exact version | Immutable |
+| `v0.12.3` | Exact version | Immutable |
 | `0.5` | Major.Minor | Points to latest patch |
 | `0` | Major only | Points to latest minor |
 | `latest` | Most recent release | Mutable - not recommended for production |
@@ -108,15 +108,15 @@ The Helm chart version is kept in sync with the application version:
 
 | Chart.yaml Field | Value |
 |------------------|-------|
-| `version` | `0.12.1` (chart version, no `v` prefix) |
-| `appVersion` | `v0.12.1` (app version, with `v` prefix) |
+| `version` | `0.12.3` (chart version, no `v` prefix) |
+| `appVersion` | `v0.12.3` (app version, with `v` prefix) |
 
 ### Image Tag Resolution
 
 The Helm chart resolves the image tag in this order:
 
-1. **Explicit override**: `--set image.tag=v0.12.1`
-2. **Chart's appVersion**: Automatically uses `v0.12.1` when installing `--version 0.12.1`
+1. **Explicit override**: `--set image.tag=v0.12.3`
+2. **Chart's appVersion**: Automatically uses `v0.12.3` when installing `--version 0.12.3`
 
 ## Best Practices
 
@@ -127,14 +127,14 @@ The Helm chart resolves the image tag in this order:
 ```bash
 # Install specific chart version (uses matching image tag automatically)
 helm install tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   ...
 ```
 
 Or explicitly set the image tag:
 ```bash
 helm install tns-csi ./charts/tns-csi-driver \
-  --set image.tag=v0.12.1 \
+  --set image.tag=v0.12.3 \
   ...
 ```
 
@@ -160,7 +160,7 @@ kubectl logs -n kube-system deployment/tns-csi-controller | head -1
 Upgrade to a new version:
 ```bash
 helm upgrade tns-csi oci://registry-1.docker.io/bfenski/tns-csi-driver \
-  --version 0.12.1 \
+  --version 0.12.3 \
   --reuse-values
 ```
 
@@ -178,6 +178,6 @@ kubectl exec -n kube-system deployment/tns-csi-controller -- \
 ```
 
 Include in your issue:
-- Version (e.g., `v0.12.1`)
+- Version (e.g., `v0.12.3`)
 - Git commit (e.g., `abc1234`)
 - How you installed (Helm version, custom image, etc.)