From 32923a67a6467e712cb3bc4720745242da875b44 Mon Sep 17 00:00:00 2001 From: Oren Fromberg Date: Thu, 2 Jul 2026 10:10:17 -0400 Subject: [PATCH] chore: bump chart version to 0.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Triggers the release workflow to publish nebari-nebi-pack-0.1.1. Changes since 0.1.0 (one merged PR): - #38 — expose `orgCABundle.configMapName` for TLS trust injection. Adds an optional value that, when set, mounts a pre-provisioned ConfigMap of PEM CA certs into the nebi pod at `/etc/ssl/certs/org-ca.crt` and sets `SSL_CERT_FILE`. Backwards- compatible: `helm template` output is byte-identical when the value is left at its empty default. Required on clusters with a TLS- intercepting egress proxy (pixi/rattler fail with "unknown CA" otherwise). Mirrors the pattern in nebari-rayserve-pack#16. Versioning note: this is a single backwards-compatible feature add. Strict semver would call for a minor bump (0.2.0); using a patch bump here matches the project's pre-1.0 convention where the 0.1.0-alpha.N line rolled feature additions through patch-level increments. Bump to 0.2.0 instead if the maintainer prefers strict semver — the release workflow keys off whatever is in Chart.yaml. `appVersion` stays at "0.13" — the nebi image hasn't changed, only the chart's rendering does. --- Chart.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Chart.yaml b/Chart.yaml index 1b664e7..cf882e0 100644 --- a/Chart.yaml +++ b/Chart.yaml @@ -2,5 +2,5 @@ apiVersion: v2 name: nebari-nebi-pack description: A Helm chart for deploying Nebi (environment management platform) on Nebari type: application -version: 0.1.0 +version: 0.1.1 appVersion: "0.13"