chore(master): release ontoserver 0.5.2

.release-please-manifest.json

@@ -1,5 +1,5 @@
 {
-  "charts/ontoserver": "0.5.1",
+  "charts/ontoserver": "0.5.2",
   "charts/ontoserver-extras": "0.1.2",
   "charts/ontoserver-indexer": "0.2.1"
 }

CLAUDE.md

@@ -50,7 +50,7 @@ The traps, in short:
   without it Release Please rewrites a release branch only when the generated *release notes*
   change, so a straggler keeps a stale base and conflicts. Don't remove that flag.
 
-Current releases: `ontoserver` 0.5.1, `ontoserver-extras` 0.1.2, `ontoserver-indexer` 0.2.1.
+Current releases: `ontoserver` 0.5.2, `ontoserver-extras` 0.1.2, `ontoserver-indexer` 0.2.1.
 
 ## Editing a chart
 

RELEASE.md

@@ -374,7 +374,7 @@ generated GitHub Release notes carry that information.
 
 | Chart | Latest release | Notes |
 |---|---|---|
-| `ontoserver` | **0.5.1** | Removes `deployment.allowScaledReadWrite` — scaled read-write is not supported. 0.5.0 added `deployment.podManagementPolicy` and the OTel metrics/logs exporter values, and restored the empty `serverPort` default |
+| `ontoserver` | **0.5.2** | Scaled read-write is not supported: 0.5.1 removed `deployment.allowScaledReadWrite`, 0.5.2 stops the config passthroughs re-enabling writes. 0.5.0 added `deployment.podManagementPolicy` and the OTel metrics/logs exporter values, and restored the empty `serverPort` default |
 | `ontoserver-extras` | **0.1.2** | |
 | `ontoserver-indexer` | **0.2.1** | |
 

charts/ontoserver/Chart.yaml

@@ -3,7 +3,7 @@ name: ontoserver
 description: Ontoserver FHIR terminology server helm chart with various
   deployment configurations
 type: application
-version: 0.5.1
+version: 0.5.2
 appVersion: "ctsa-6"
 home: https://ontoserver.csiro.au
 icon: https://raw.githubusercontent.com/aehrc/ontoserver-deploy/master/icons/ontoserver.png
@@ -24,7 +24,5 @@ annotations:
   # Please, not an in-development one. Release Please bumps `version:` but does NOT touch this list,
   # so update it in the release PR before merging or it will silently describe the previous release.
   artifacthub.io/changes: |
-    - kind: removed
-      description: 'Scaled read-write is NOT supported and there is no opt-in. Removes ontoserver.deployment.allowScaledReadWrite and the two scaled read-write example values files that used it. A values file setting that flag with type scaled and isReadOnly false now fails to render'
-    - kind: changed
-      description: 'Documentation now states up front that scaled deployments are read-only and that scaled read-write is unsupported, instead of presenting it as an opt-in topology'
+    - kind: fixed
+      description: 'Scaled read-write is NOT supported. An ontoserver.config or ontoserver.secretConfig entry can no longer re-enable writes on a scaled deployment - such an entry took effect over the chart at runtime, and now fails to render instead'

charts/ontoserver/changelog.md

@@ -5,6 +5,13 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.5.2](https://github.com/aehrc/ontoserver-deploy/compare/ontoserver-v0.5.1...ontoserver-v0.5.2) (2026-08-14)
+
+
+### Fixed
+
+* **ontoserver:** stop config passthroughs re-enabling writes on scaled deployments ([fd908cd](https://github.com/aehrc/ontoserver-deploy/commit/fd908cd29c72841decfbaaa13d3b230c7763bed8))
+
 ## [0.5.1](https://github.com/aehrc/ontoserver-deploy/compare/ontoserver-v0.5.0...ontoserver-v0.5.1) (2026-08-13)