update old with version number

Signed-off-by: Mohammed Abdi <mohammed.munir.abdi@ibm.com>

Author: mamy-CS

README.md

@@ -169,7 +169,7 @@ helm upgrade workload-variant-autoscaler ./charts/workload-variant-autoscaler \
 ### Breaking Changes
 
 #### v0.5.0 (upcoming)
-- **VariantAutoscaling CRD**: Added `scaleTargetRef` field as **required**. Old VariantAutoscaling resources without `scaleTargetRef` must be updated before upgrading:
+- **VariantAutoscaling CRD**: Added `scaleTargetRef` field as **required**. v0.4.1 VariantAutoscaling resources without `scaleTargetRef` must be updated before upgrading:
   - **Impact on Scale-to-Zero**: VAs without `scaleTargetRef` will not scale to zero properly, even with HPAScaleToZero enabled and HPA `minReplicas: 0`, because the HPA cannot reference the target deployment.
   - **Migration**: Update existing VAs to include `scaleTargetRef`:
     ```yaml

docs/CHANGELOG-v0.5.0.md

@@ -178,7 +178,7 @@ query := fmt.Sprintf(`vllm_kv_cache_usage{namespace="%s"}`, escapedNamespace)
 - The controller skips processing VAs without `scaleTargetRef.name` (see `internal/utils/variant.go`).
 
 **Impact on Scale-to-Zero:**
-- **Critical**: Old VAs without `scaleTargetRef` will **not scale to zero** properly, even if:
+- **Critical**: v0.4.1 VAs without `scaleTargetRef` will **not scale to zero** properly, even if:
   - HPAScaleToZero feature gate is enabled
   - HPA has `minReplicas: 0` configured
   - Scale-to-zero is enabled in WVA configuration