Skip to content

Guardana Control 0.10.2-alpha

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 10 Oct 07:36
· 132 commits to main since this release
Immutable release. Only release title and notes can be modified.

Fixes and release tooling from an outside audit of 0.10.0-alpha, with no new
feature: react no longer times a whole pass by its lock wait, the release
scans every binary it ships before attesting it, the website names the
published release rather than the next one, the repository's GitHub settings
have a read-only check, and a pause file replaced during a read is read
again. 0.10.1-alpha was tagged with most of these changes and never
published: its release job stopped at the new image scan.

Added

  • The release scans every binary it ships before anything is attested or
    published: each binary of every archive and the image's binary for
    linux/amd64 and linux/arm64, with govulncheck in binary mode
    (scripts/scan-binaries.sh). A known vulnerability, or a scan that could
    not run, stops the release; the dry run scans its archives and image too.
  • An issue template for a report from trying it with your own MCP client and
    server.
  • docs/reference/versions.md lists every format
    a user writes or reads with the version this release writes, the versions it
    reads and its stability, held to the code's constants by a test. The wire
    contract's 1.0 is the one stable format; the product is still 0.x.

Changed

  • The website names the published release, which docs/docs.json sets once a
    release is out, rather than the newest dated section of this file, and each
    page's footer links that release's documentation at its tag
    (ADR-0049). The site
    had named 0.10.0-alpha a day before it was published.
  • The home page leads with what runs today, a gateway that decides MCP tool
    calls, states what it does not cover, and says what each planned task
    brings. It no longer says the product watches by default: the enforcement
    mode has no default
    (ADR-0032).
  • The repository's GitHub settings are declared once, in
    scripts/lib/github-settings.sh: scripts/github-bootstrap.sh applies them,
    and scripts/github-settings-check.sh compares them with GitHub without
    writing (rulesets, required checks, bypasses, who holds maintain or admin,
    labels and milestones), exiting 1 on drift and 2 when something could not be
    read. Two approvals and code-owner review now also cover adapters/authzen/
    and adapters/mcp/; the paths are spread over rulesets of at most 15
    patterns each, GitHub's limit per reviewer, which the bootstrap checks
    before it writes anything. Milestones follow the roadmap, and labels use
    GitHub's good first issue and help wanted.
  • CI's quality job may run 45 minutes; its fuzz smoke alone took 14 of the 30
    it had.

Fixed

  • A plane reading the pause file while a writer replaced it, as
    guardana-control pause add and remove and most editors do, turned the
    pause state unknown for a poll interval and blocked every call meanwhile. A
    read that finds the file replaced between judging its name and opening it
    now starts again, up to three times in all, with every check each time; a
    link swapped in is still refused and a file replaced at every attempt is
    still unknown.
  • The release job's image scan pulled every platform of the image by the
    index's digest, which Docker's default image store refuses for a second
    platform ("cannot overwrite digest"), so 0.10.1-alpha's release stopped
    before it attested or published anything. Each platform is now pulled by
    its own manifest's digest.
  • react gave its whole pass the ten seconds meant for waiting on another
    writer's lock, so a pass over a list near its bound, judged again before
    each line, could end with context deadline exceeded while no other writer
    ran. Each line now waits up to ten seconds for the lock and nothing else is
    timed. A wait that runs out, or an interrupt, now ends the pass after the
    lines already written; react prints them and its count line, then exits 1.
    Once the list refuses a line for its bounds, react names every later
    finding as not written without taking the lock again, so a long pass over
    a full list no longer shuts out stops lift.

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