Releases

Oriel release artifacts are published under arbor.klado.dev. Production deployments should pin chart and image versions together unless you are deliberately testing a custom image against a known chart.

Pull the current stable image:

docker pull arbor.klado.dev/oriel/oriel:latest

Release candidates are published as immutable prerelease tags and as the moving :rc image tag. The :latest image tag is stable-only and never points to a release candidate.

docker pull arbor.klado.dev/oriel/oriel:<version>-rc.1
docker pull arbor.klado.dev/oriel/oriel:rc

Use the Helm repository:

helm repo add oriel https://arbor.klado.dev/api/packages/oriel/helm
helm repo update
helm install oriel oriel/oriel

List published chart versions:

helm search repo oriel/oriel --versions

Install a specific stable release by pinning the chart version:

helm install oriel oriel/oriel --version 0.2.0

Install a release candidate by pinning its immutable chart version:

helm install oriel oriel/oriel --version <version>-rc.1

Use pinned stable version tags for production deployments. The production Compose file stays pinned to stable releases; test a release candidate by overriding the image tag explicitly instead of changing deploy/compose/prod.yml.

Maintainers create release candidates either by running the release-pr workflow with channel=rc, or by merging a pull request labeled Kind/Prerelease. Candidate tags are immutable. If a candidate is bad, publish the next -rc.N tag rather than moving an existing tag.