Release Hub chart 0.169.1 with HTTP port recovery guidance

Publish the hardened-image port migration documentation from #217. Keep runtime defaults unchanged and clarify that the recovery helper requires a repository checkout and explicit execution. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-11-05 20:20:24 +00:00 · 2026-11-04 09:43:57 +00:00
2 changed files with 5 additions and 1 deletions
@@ -16,7 +16,7 @@ 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.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.169.0
+version: 0.169.1

 # 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
@@ -130,6 +130,10 @@ legacy defaults, hardened runtime/probes, and unchanged OAuth2 routing.

 ### Recovering a duplicate HTTP port during upgrades

+Chart `0.169.1` publishes this recovery guidance. The helper is available in the
+repository's `scripts/` directory, not in the chart archive. This release does
+not automatically migrate live container ports or change runtime defaults.
+
 An upgrade changing a container's HTTP port from `80` to `8080` can fail with
 `spec.template.spec.containers[0].ports[1].name: Duplicate value: "http"`.
 Kubernetes strategic merges identify container ports by number, not name: