Release Channels
Each release channel identifies a product set. Sensor and Team Server keep separate semantic versions and are compatible when their major versions match.
Choose a Channel
| Channel | Purpose | Movement |
|---|---|---|
latest | Newly published artifacts awaiting full deployment validation | Updated by the product release workflows |
testing | The exact latest product set that passed the deployment test matrix | Promoted from latest only |
stable | The approved testing product set for production use | Promoted from testing only |
Promotion rejects older destination product versions. Repeating it requires identical product artifacts.
Use testing in evaluation, automation, and container examples unless your organization has selected another channel. Use stable for production after validating it in your environment.
Artifact Naming
Native Runtime Sensor installers and package repositories select the channel by name:
https://repo.endurasecurity.com/install/endura-sensor/testing.sh
https://repo.endurasecurity.com/testing/endura-sensor/Images have mutable channel tags and immutable version tags; channel-tracking examples use testing:
ghcr.io/endurasecurity/container/endura-sensor:testing
ghcr.io/endurasecurity/container/endura-team-server:testingUse a semantic-version tag instead only when a non-Kubernetes deployment must remain on one immutable release.
Helm uses a channel namespace and a product-specific OCI repository with an explicit semantic version. OCI Helm charts do not use channel names as tags:
oci://ghcr.io/endurasecurity/helm/testing/endura-sensor --version 1.0.121
oci://ghcr.io/endurasecurity/helm/testing/endura-team-server --version 1.0.85Each chart defaults to the immutable container image version in its appVersion. Do not override image.tag with a mutable channel tag in Kubernetes.
Inspect a Channel
Each promoted repository supplies release.json with product versions, image identities, chart references, and checksums:
curl -sSf https://repo.endurasecurity.com/testing/release.jsonUse this manifest when automation must resolve a channel once and deploy the same product set across multiple hosts or clusters.
Pinning and Updates
Mutable native-package channels and container tags are convenient for hosts that deliberately track a channel. Pin semantic versions when reproducibility matters.
Kubernetes deployments must always pass the chart version explicitly. To update a deployment, read the destination channel manifest, review Runtime Sensor and Team Server compatibility, then upgrade each chart to the versions recorded in that manifest.