chore(release): v0.39.0 (#1185)

Author: vmyroslav

CHANGELOG.md

@@ -2,6 +2,8 @@
 
 ## [MAJOR.MINOR.PATCH] - YYYY-MM-DD
 
+## v0.39.0 - 2026-05-29
+
 - Add `KafkaSchema` field `references[].kafkaSchemaRef`, type `object`: Reference to another
   `KafkaSchema` resource in the same namespace. The subject and version are resolved from the
   referenced resource's spec and status, dependents pick up new versions automatically.

charts/aiven-operator-crds/Chart.yaml

@@ -2,8 +2,8 @@ apiVersion: v2
 name: aiven-operator-crds
 description: A Helm chart to deploy the aiven operator custom resource definitions
 type: application
-version: v0.38.0
-appVersion: v0.38.0
+version: v0.39.0
+appVersion: v0.39.0
 maintainers:
   - name: byashimov
     url: https://www.aiven.io

charts/aiven-operator/Chart.yaml

@@ -2,8 +2,8 @@ apiVersion: v2
 name: aiven-operator
 description: A Helm chart to deploy the aiven operator
 type: application
-version: v0.38.0
-appVersion: v0.38.0
+version: v0.39.0
+appVersion: v0.39.0
 maintainers:
   - name: byashimov
     url: https://www.aiven.io

docs/docs/changelog.md

@@ -1,6 +1,17 @@
 # Changelog
 
 
+## v0.39.0 - 2026-05-29
+
+- Add `KafkaSchema` field `references[].kafkaSchemaRef`, type `object`: Reference to another
+  `KafkaSchema` resource in the same namespace. The subject and version are resolved from the
+  referenced resource's spec and status, dependents pick up new versions automatically.
+  Mutually exclusive with `subject` + `version` on the same entry.
+- Change `KafkaSchema` field `references`: maxItems `100`
+- **BREAKING**: Change `KafkaSchema` deletion to perform a hard delete instead of soft delete only.
+  The subject is no longer visible in the registry's listing after deletion,
+  and re-applying a `KafkaSchema` with the same `subjectName` after deletion starts at version 1.
+
 ## v0.38.0 - 2026-05-18
 
 - Add `MySQL` and `PostgreSQL` field `migrationSecretSource`, type `object`: Reference to a Secret containing migration