feat(relay-control): deployment default sharing mode and Control 0.5.35 (relay-control 0.4.23, agent-relay 0.7.68)
KH
1d ago+246+246+012345678901234567890123456789-68-68-01234567890123456789
What
- Deployment default session-sharing mode. Two optional values, unset by default, which keeps Control's built-in behaviour.
| Value | Env on the Control api container | Accepted |
|---|---|---|
sharing.defaultMode (relay-control.sharing.defaultMode under agent-relay) | SELFHOST_DEFAULT_SHARING_MODE | all, new, selected; empty = unset |
sharing.overrideRoles | SELFHOST_SHARING_MODE_OVERRIDE_ROLES (comma list) | list from owner, admin; empty = unset |
The render refuses any other mode, a non-list, an unknown role or a duplicate role. The chart default stays unset. owner,admin belongs only in the install values of the customer that asked for it.
- Control 0.5.35. This is the first image with relay-control#232. The chart default and the EKS, EKS RDS-native, GCP, gcp-proof-live and kind-core profiles move from 0.5.24 (
sha256:d1b6ca95, edad643) to 0.5.35:
ghcr.io/agentworkforce/relay-control@sha256:1cb5bd714e7c9f326cfe107544b8b7125207c80a7e556ab8debf78a8b2167ad9, built from b985c6f by publish run 44492248387.- I verified it here:
gh attestation verifypasses;- amd64 and arm64 pull anonymously;
- the OCI revision label is b985c6f on both platforms;
- the Cmd is unchanged (
node node_modules/relay-control/dist/server.js).
- Over 0.5.24, from layered-control's reading of the source diff:
- migrations 0052-0065 and 0067-0077, with no operator step;
- 0057 rewrites two small Desktop identity tables;
- 0074 is a one-UPDATE backfill;
- 0073 validates a constraint on
admin_audit_eventsunder a short lock; - no new required env or Secrets, and 20 new optional names.
- History origins now live in
SELFHOST_RELAYHISTORY_AUDIENCES. A History origin left inSELFHOST_INTROSPECT_AUDIENCESonly produces a startup warning. - License: FSL-1.1-ALv2 from Control 0.5.28 on. Khaliq approved it for self-hosted distribution on 2026-11-19. The customer image record is updated.
- No upgrade from a 0.5.24 database has been tested yet. Per Khaliq's direction, 0.5.35 goes to dev first.
Hold
merge-train:hold stays until 0.5.35 is proven in dev (infra-environments is preparing that pin) or Khaliq says to merge. This PR deploys nothing.
Changes
- relay-control 0.4.23 and agent-relay 0.7.68 (lock), with main merged in at 0.7.67.
- EKS Ingress
controlPathsre-checked against the 0.5.35 source; the ten paths still cover it. New in 0.5.35: websocketGET /relay-node/v1/ws(under the existing/relay-nodeprefix) and Replicas/admin routes under/api/v1. This was a source read, not a live test, and the ALB idle timeout for the new websocket is unchecked. - Values, validation and env.
- Profile pins.
- Customer image record and release evidence hash.
- Supply-chain doc.
- Subdomain golden: only the Control digest and its hash-named migration Jobs move.
ci/control-sharing/test_chart.py.- Registry option
opt.relay-control.sharing-mode.
Checks run locally
- control-sharing, control-analytics, native-no-relayauth, native-history-connection, release-candidate, control-webapp-names and history-upload: pass.
- Customer release gate tests: PASS (38 cases).
- Registry check: OK.
- Subdomain golden: OK.
- Version bump check: OK.
helm lint: OK.
🤖 Generated with Claude Code