Skip to content

chore: bump chart version to 0.1.1#39

Merged
pmeier merged 1 commit into
nebari-dev:mainfrom
oren-openteams:chore/bump-chart-0.1.1
Jul 2, 2026
Merged

chore: bump chart version to 0.1.1#39
pmeier merged 1 commit into
nebari-dev:mainfrom
oren-openteams:chore/bump-chart-0.1.1

Conversation

@oren-openteams

Copy link
Copy Markdown
Contributor

Summary

Bumps Chart.yaml version 0.1.0 -> 0.1.1 to trigger the release workflow and publish nebari-nebi-pack-0.1.1.

What's in this release (vs 0.1.0)

One merged PR since the last release:

  • feat: expose orgCABundle.configMapName for TLS trust injection #38feat: expose orgCABundle.configMapName for TLS trust injection
    Adds an optional orgCABundle.configMapName value. When set, the chart mounts the named ConfigMap into the nebi pod at /etc/ssl/certs/org-ca.crt and sets SSL_CERT_FILE to point at it. Required on clusters with a TLS-intercepting egress proxy whose CA isn't in the container's default trust store (pixi/rattler outbound HTTPS to conda-forge / pypi / github otherwise fails with unknown CA). Mirrors the pattern in nebari-rayserve-pack#16.

Backwards-compatible. helm template output is byte-identical when orgCABundle.configMapName is left at its empty default — no existing deployment sees any diff. Only operators who opt in by setting the value get the new mount.

Versioning choice

This is one additive, backwards-compatible feature. Two defensible bumps:

  • Patch (0.1.1) — what this PR uses. Matches the pre-1.0 convention where feature additions have historically rolled through patch-level increments (see the 0.1.0-alpha.N sequence in the tag history).
  • Minor (0.2.0) — what strict semver would call for, since we're adding a new public value to the chart's API.

Happy to change to 0.2.0 if you prefer strict semver — the release workflow keys off whatever is in Chart.yaml, so it's a one-line edit before merge.

appVersion

Unchanged ("0.13") — the nebi container image hasn't changed, only the chart-side rendering does.

What happens after merge

Per .github/workflows/release.yaml, a push to main that changes Chart.yaml triggers:

  1. helm package . produces nebari-nebi-pack-0.1.1.tgz
  2. GitHub release created as nebari-nebi-pack-0.1.1, tarball attached, notes auto-generated from PR titles
  3. gh-pages branch's helm repo index updated to include the new version
  4. Chart becomes installable via helm install nebi nebari/nebari-nebi-pack --version 0.1.1 and via the OCI artifact at oci://quay.io/nebari/charts/nebari-nebi-pack --version 0.1.1

No other manual steps.

Triggers the release workflow to publish nebari-nebi-pack-0.1.1.

Changes since 0.1.0 (one merged PR):

- nebari-dev#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.
@oren-openteams oren-openteams requested a review from pmeier July 2, 2026 14:50
@pmeier pmeier merged commit 1de086e into nebari-dev:main Jul 2, 2026
4 of 5 checks passed
@oren-openteams oren-openteams deleted the chore/bump-chart-0.1.1 branch July 2, 2026 15:41
@oren-openteams oren-openteams mentioned this pull request Jul 7, 2026
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants