How to test the chart and publish a version.
python3 -m venv .venv
.venv/bin/pip install -r requirements-dev.txt
GOBIN="$PWD/.bin" go install github.com/batchstream/weir/cmd/weir@SOURCE_REVISION
make test PYTHON=.venv/bin/python WEIR_BIN="$PWD/.bin/weir"
make package PYTHON=.venv/bin/python WEIR_BIN="$PWD/.bin/weir"SOURCE_REVISION is the weir.batchstream.io/source-revision annotation in Chart.yaml. make test lints the Chart, renders every example and validates the generated configuration with the selected Weir binary, including a scale check with many Stores and replicas and an isolated loopback-only serve, HTTP probe and shutdown run. With an official promtool on PATH or named by PROMTOOL, it also runs the rendered alerts and the autoscaling query against their PromQL fixtures; CI installs a checksum-verified promtool. It opens no backend connections, reads no existing Secrets and does not exercise CNI enforcement, Prometheus collection or KEDA scaling in a real cluster.
CI also runs scripts/kind-rollout.sh on every change. In a kind cluster of its own, under load from weir-soak with -no-errors, it rolls a release of this checkout's Chart out twice at one replica, replaces the replica with one that starts 30 seconds late, scales to three replicas, rolls the three out twice and scales back down. The change fails if a rollout does not complete, a caller saw any error or an outcome did not hold. Every rollout setting stays the Chart's default, and the test measures no throughput. To run it locally, build weir-soak for the cluster's platform from a weir-tests checkout at the revision ci.yaml installs. The script uses a kubeconfig of its own and ignores your current context and Helm settings. For kind on an arm64 Mac:
(cd path/to/weir-tests && GOOS=linux GOARCH=arm64 CGO_ENABLED=0 go build -o weir-soak ./cmd/weir-soak)
scripts/kind-rollout.sh path/to/weir-tests/weir-soakA reviewed weir-VERSION tag on main publishes the OCI Chart and a GitHub release with the archive and SHA256SUMS. The workflow refuses a version whose OCI Chart already exists and creates the release before pushing, so a rerun never overwrites a published Chart. If the push fails after the release exists, verify the release archive against its SHA256SUMS and helm push it by hand. Source annotation, image digest and CI source pins must identify the same server revision.