Release Process
A Racora release is a version tag, vX.Y.Z. Cutting it resolves the latest published
version of each external component (the gNB image, the Open5GS image, CU-IP), builds
Racora's own images at their own versions, mirrors every image and the pinned upstream k3s
binary into Racora's registries, bakes the image pins into the chart, and publishes the
release with these assets:
| Asset | What it is |
|---|---|
racora-X.Y.Z.tgz | the Helm chart with the pins baked into its defaults; also pushed as an OCI artifact |
racora-crds.yaml | the NRCell and Subscriber CRDs, one file |
chart-values.yaml | the release pins as values |
racora-installer-vX.Y.Z.tar.gz | the installer package: the front door, the platform and core modules, the node provisioner, the node contract |
k3s, sha256sum-amd64.txt, k3s-version.txt | the upstream k3s release, mirrored and checksum-verified |
SHA256SUMS | covers the chart, CRDs, pins, installer package and k3s version |
The offline image archive is built separately, on request, for a release; a release whose page lists no archive installs online only (Use Your Own Registry or Install Offline).
Every change is gated in CI before it merges, and every tag runs the integration suites, which install the RAN on each supported platform, declare cells and subscribers, and upgrade from the previous published release.
Published releases start at v0.6.0. They are listed, with the component versions each one pins, on Release History; how versions relate is Versions and Compatibility.