Skip to content

chore: pin the 2026-10-29 stable subcharts - #25

Merged
leandrolerena merged 1 commit into
mainfrom
chore/pin-stable-2026-10-29
Oct 29, 2026
Merged

leandrolerena merged 1 commit into
mainfrom
chore/pin-stable-2026-10-29

Conversation

@leandrolerena

Copy link
Copy Markdown
Member

Pins the umbrella chart's Neops subcharts to the 2026-10-29 stable release and bumps the umbrella version from 0.1.0 to 0.2.0:

Subchart From To
neops-core 2.2.1-beta.9 2.3.0
neops-workflow-engine 0.43.0-beta.10 0.44.0
neops-monitor-app 0.43.0-beta.10 0.44.0
neops-worker 0.2.0-beta.8 0.3.0
neops-web-client 6.0.0-beta.2 6.0.0
neops-secure-gateway 0.4.1-beta.2 0.4.1
neops-storage 0.0.8-beta.7 0.0.8

Worker 0.2 does not work with a 0.44 engine, because the engine accepts only clients in ^0.44.0. That is why the engine and the worker move together.

In "Upgrading core", README.md now says "Since core chart 2.3.0". It links "The rebuild runs on upgrade" in core's docs/releases/v2.3.0.md at the v2.3.0 tag, where it used to link unreleased.md.

As a small cleanup, the chart description and a comment in charts/neops/Chart.yaml now spell the name "Neops".

Verification

Helm CI runs only the label check, so I checked these by hand:

  • Every pinned chart version exists under quay.io/zebbra/charts/<name>, checked through the Quay API.
  • I copied the chart and ran helm dependency update, helm lint and helm template with the default values in alpine/helm (Helm v4.3.1).
    • All the OCI dependencies pulled.
    • Lint reported no failures, only the usual "icon is recommended" note.
    • The rendered manifests reference neops-core:2.3.0, neops-workflow-engine:0.44.0, neops-monitor-app:0.44.0, neops-worker-sdk:0.3.0, neops-web-client:6.0.0 and neops-secure-gateway:0.4.1. Storage is disabled by default, so it renders no image.

I did not run make local-deploy / make local-upgrade on KIND, and I did not lint with values-kind.yaml.

….2.0

Pins neops-core 2.3.0, workflow-engine and monitor-app 0.44.0, worker 0.3.0,
web-client 6.0.0, secure-gateway 0.4.1 and storage 0.0.8. The README links
core's v2.3.0 release notes instead of unreleased.md.
@leandrolerena leandrolerena added the pr-other PR does something not covered by other labels label Oct 29, 2026
@leandrolerena leandrolerena self-assigned this Oct 29, 2026
@leandrolerena
leandrolerena merged commit 2bc1a4f into main Oct 29, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-other PR does something not covered by other labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant