Versioning & Support

How Actyze is versioned

Actyze follows Semantic Versioning: MAJOR.MINOR.PATCH.

Bump	Means
MAJOR	Backwards-incompatible change to the API or values surface
MINOR	New functionality, backwards compatible
PATCH	Bug fix or security fix. No new features

We are pre-1.0. While on 0.x, treat 0.MINOR.x as the line that may carry both features and occasional unavoidable breaking changes, and 0.x.PATCH as fixes only. We move to 1.0.0 when the API and values surface are declared stable.

Lockstep versioning

Actyze ships six images:

• actyze/dashboard-nexus
• actyze/dashboard-frontend
• actyze/dashboard-schema-service
• actyze/prediction-worker-xgboost
• actyze/prediction-worker-lightgbm
• actyze/prediction-worker-autogluon

They share one version number. A release tags all six with the same X.Y.Z, even if a given image did not change that cycle. That same version is the Helm chart's appVersion.

This means "what version am I running?" has a single answer. It also means an image may be republished with an unchanged content — that is expected.

Chart version vs appVersion

Field	Meaning
version	The Helm chart's own version. Changes when the chart's templates or values change.
appVersion	The Actyze release the chart deploys. Equals the image tag.

The two move independently: a chart-only fix bumps version but not appVersion.

Image tag policy

Pin to an immutable version tag. The chart and the published Compose file default to a specific version with pullPolicy: IfNotPresent:

image:
  repository: actyze/dashboard-nexus
  tag: "0.1.1"
  pullPolicy: IfNotPresent

Avoid latest and branch tags such as main. They are not reproducible, cannot be rolled back to a known state, and can change under a running deployment without any action on your part — including between two pods of the same deployment, if one node has an older copy cached.

Which versions get fixes

Actyze is pre-1.0 and maintained by a small team. Only the latest release receives security and bug fixes. There is no backport branch and no long-term support line yet.

In practice this means staying current is the supported path. Upgrades between patch releases are intended to be uneventful; see Upgrading for anything that needs your attention.

Release history

Version	Date	Summary
0.1.1	Aug 2026	Security and reliability. Container hardening, SBOM and vulnerability gating in CI, non-root images. Fixes prediction workers that did not start in 0.1.0.
0.1.0	Jul 2026	First tagged release. Observability across all services, versioning and release process codified.

Full notes for every release are published on GitHub Releases.

Verifying what you are running

# Helm
helm list -n actyze                      # chart version
helm get metadata dashboard -n actyze    # includes appVersion

# Kubernetes — the image tags actually running
kubectl get pods -n actyze \
  -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[0].image}{"\n"}{end}'