Skip to content

Guardana Control 0.4.0-alpha

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 01 Oct 20:27
· 312 commits to main since this release
Immutable release. Only release title and notes can be modified.

An operator can now open runs for an agent, and a plane with runs.dir
accepts a call only under a run token that resolves: two runs of one agent
keep their flow state apart, and a run's flow state survives a restart. A
plane without runs.dir behaves as before. A stdio plane no longer writes its
start lines into the protocol stream.
docs/status.md says what is implemented and what is
experimental. Nothing here is a security boundary yet.

Added

  • Runs an operator opens
    (ADR-0034):
    guardana-control runs open, close and list over a runs directory, and
    runs.dir on the plane, under which every call needs a run token, in the
    Run-Token header on HTTP or from run --run-token-file on stdio. Two
    runs of one agent keep their flow state apart, a run opened under a parent
    shares the flow state of the parent's top-level run, the state survives a
    restart, and a held call resumes only from its own run. A refused token is
    answered with HTTP 401 or the JSON-RPC error -31102, and the refusals are
    counted by cause. A plane without runs.dir is unchanged.

Changed

  • The release job waits for a maintainer to approve it in the release
    environment before it builds; RELEASING.md has the step.

Fixed

  • A plane with a stdio listener wrote its start lines, the mode and the count
    of held calls lost to a restart among them, to standard output, which is the agent's protocol stream,
    so a client's first read failed; they now go to standard error.

Image: ghcr.io/guardana/control-gateway@sha256:d69a32976fd152ed316aa44ea2fcb1594f15773a212c7ca099084625cdd610c0