Repository navigation
0.1.0-alpha.2 - 2026-11-07
Pre-release
Pre-release
Release Notes
Added
- Agent: a failed flow's device logcat is uploaded as an excerpt: the lines of the failing step's window (10 s before it to 2 s after it), redacted line by line, at most 512 KiB, keeping the newest lines and saying when older ones were cut. The window is placed on UTC by the log's own last line, so a log whose clock cannot be told from the failure's is not sent (#75).
- Agent: an app that crashes during a flow is journaled as
app.crashed(package and exception, from Maestro'scrash-report.txt) on that flow. The flow's verdict stays Maestro's own (#75). - Server: the
device_logcatartifact class, a text file with its own size limit (artifacts.max_bytes.device_logcat, 512 KiB) (#75). - Dashboard: screen D offers a failed flow's device logcat excerpt as a download, labelled "Device logcat excerpt" (#75).
- Agent: at run end,
GITHUB_STEP_SUMMARYgets a short Markdown summary: outcome counts, the flows that did not pass with their provenance and reason, and a dashboard link whenFLEET_SERVERis set. A summary that cannot be written costs one notice; Maestro's output and exit status never change (#71). - Agent: the devices Maestro drives are sampled every 30 s with one read-only adb probe each: adb's state, whether
sys.boot_completedis set, and the guest's CPU and available memory (guest, unknown when adb does not answer). The server stores them indevice_samplesand screen C serves them (#39). - Examples: a composite GitHub Action,
examples/github-actions/fleet-agent, installs a pinned, checksum-verified agent release and runs a Maestro command under it (#71). - Dashboard: a flow's stats panel says how many of its failed runs a lost device excluded from flakiness (
excludedon the flow's verdict; "2 runs excluded (device lost)"), and says nothing when there are none (#72). - Agent: a failing step's UI hierarchy (
screen-hierarchy/step-NNN-….json) is uploaded as afailure_hierarchyartifact with its on-screen text values replaced by[REDACTED](the tree and its attributes are kept); screen D lists it under its step, and the failing step's comes first (#74). - Agent: step events carry
depth,parentandattemptwhere Maestro's log shows them (a step insiderunFlow,retryorrepeat, and the retry attempt that ran it). The flow page nests steps under their block and shows the attempt of a retried step, fromGET /api/v1/projects/{project}/flows/{execution}, whosestepsare now a tree withchildren(#38). - Server: per-IP limits on the pre-auth routes (agent token exchange, browser sign-in and callback) and per-credential limits on agent connections, answered with
429 Too Many RequestsandRetry-After; an agent socket's events are paced, never dropped. Client IPs come fromtrusted_proxies(#35). - Server: viewer REST reads and live socket upgrades are limited per viewer credential (a viewer token or a browser session), answered with
429 Too Many RequestsandRetry-After; the dashboard waits that long and keeps its last data instead of erroring (#35).
Changed
- Dashboard: the pipeline's plan table reads a small plan endpoint (
GET /api/v1/projects/{project}/attempts/{attempt}/plans) and refetches it only when a planned shard's runs change or the attempt ends, instead of the whole attempt snapshot on every live update; its own fetch error shows in the table (#115). - Server: the image takes wasm-opt, tailwindcss and wasm-bindgen from a cached build layer, pinned by checksum, so a source change no longer downloads them again and a stalled download resumes (deploy/docker).
Fixed
- Agent: reconnects to a refusing server back off again. The jitter read the clock's low nanoseconds, which are always zero on macOS, so every delay was zero and the agent retried about every 1.5 ms (3,108 attempts in 5 s); jitter now comes from OS randomness, and the server's goaway reconnect jitter, which had the same bug, too (#90).
- Agent: a failed write to
journal.jsonl(disk full, I/O error) stops the journal like the cap does: onejournal.truncatedline names the error, the run's warning names the first missing seq, andfleet-agent inspectreports it. Before, the error was dropped silently (#112). - Dashboard: a flow's evidence keeps its state when its signed links renew (about every four minutes): the screenshot zoom and selection, and the log search, stay put instead of resetting, and the evidence card no longer rebuilds on every live update of the flow. A tooltip hides on Escape from anywhere while it is shown, not only from inside its trigger (#41).
- Server: a run whose socket another instance holds shows
onlineorstalefrom its persisted contact, as on the instance holding it, instead of alwaysstale(#114). - Server: a worker's Maestro and agent figures are one series per agent run, raw and in the minute and hour aggregates, so runs that share a runner no longer merge or interleave; the runner's latest reading carries only the machine's figures. The dashboard's worker page draws one line per run (#42).
- Agent: after Maestro exits, the agent keeps draining its output while the CI log is still taking it, and gives up on an output pump after 2 s with no reads and nothing held for the log, or 10 s after the exit at most, so a backed-up log no longer loses its tail and a grandchild that keeps writing cannot hold the exit (#124).
- Server: the OpenAPI document describes a flow's nested step tree without recursing, so
GET /api/v1/openapi.jsonno longer overflows the stack;StepView.childrenis an array ofStepViewreferences.
Install fleet-agent 0.1.0-alpha.2
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/moyaver/fleet/releases/download/v0.1.0-alpha.2/fleet-agent-installer.sh | shDownload fleet-agent 0.1.0-alpha.2
| File | Platform | Checksum |
|---|---|---|
| fleet-agent-aarch64-apple-darwin.tar.xz | Apple Silicon macOS | checksum |
| fleet-agent-aarch64-unknown-linux-musl.tar.xz | ARM64 MUSL Linux | checksum |
| fleet-agent-x86_64-unknown-linux-musl.tar.xz | x64 MUSL Linux | checksum |
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo moyaver/fleetYou can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo moyaver/fleet