Telo v0.121.0

Packages

Package	Version
@telorun/cli	0.121.0
@telorun/analyzer	0.121.0
@telorun/cel	0.121.0
@telorun/debug-ui	0.6.7
@telorun/debug-wire	0.4.5
@telorun/ide-support	0.121.0
@telorun/k8s-runner	0.21.0
@telorun/kernel	0.121.0
@telorun/language-server	0.121.0
@telorun/runner-core	0.20.0
@telorun/sdk	0.121.0
@telorun/templating	0.121.0

Minor

telo run at a terminal asks for the application inputs nothing supplies instead of failing. When the only reason a root Application cannot load is that variables: / secrets: / ports: entries or the required fields of its needs have no value, the CLI asks for each one on stderr (a secret or sensitive need field without echo), the kernel decodes and validates each answer exactly as it would the same text in the environment, re-asks one it refuses with its own sentence, and the run starts. Answers are the fifth and last source — after a value supplied by name, the command line, env: and default: — and are never written to the process environment, ctx.env or a started child's environment; a need field's answer goes only into that need. Once accepted, the CLI offers to save them (default no): secrets to the sensitive env file, everything else to the other, as telo env template --write places them. A watch session keeps its answers across reloads. — cli, analyzer, debug-wire, k8s-runner, kernel, runner-core

It asks only when stdin and stderr are both terminals and --no-input (a new telo run option) is not given. Without that, the refusal is unchanged (ERR_MANIFEST_VALIDATION_FAILED, ERR_NEED_UNMET, ERR_NEED_PARTIALLY_SUPPLIED) and adds a hint naming the missing variables; Kernel.RunFailed carries them as unresolved. The kernel's load() takes the asking side as an inputResolver option. Every runner backend now starts applications with --no-input, and the oldest telo a runner supervises moves to the release carrying it.

---

Changelogs: cli · analyzer · cel · debug-ui · debug-wire · ide-support · k8s-runner · kernel · language-server · runner-core · sdk · templating