releases.shpreview
← What's New

v0.20.0

Minor Changes

  • cb55e62: releases admin source fetch now accepts --wait [seconds], blocking until the managed-agent session reaches a terminal state. Without --wait the command stays fire-and-forget. Default wait is 900s; pass an explicit value to shorten it (e.g. --wait 60).

    Exit codes:

    • 0 — session completed successfully
    • 1 — our-side error (no tools called, parser failure, timeout)
    • 2 — managed-agents/provider error (e.g. unknown_error, model_overloaded_error, retries exhausted) — the message is tagged (managed-agents · <type>) and includes retry count when the session ended in retries_exhausted
    • 130 — session cancelled

    Closes the silent-failure gap surfaced in registry #590 where backend incidents bubbled up as exit 0 even though no work happened.

  • f0eab05: releases admin overview-list lists organizations with their overview status. Pass --stale to filter to orgs whose overviews need regeneration:

    releases admin overview-list --stale
    releases admin overview-list --stale --stale-min-releases 3 --stale-grace-days 14
    releases admin overview-list --stale --json

    An org is considered stale when recentReleaseCount > minReleases AND the overview is either missing or lastActivity > overview.updatedAt + graceDays. Defaults: minReleases=5, graceDays=7.

    The --json output carries slug, name, recentReleaseCount, lastActivity, overviewUpdatedAt, and overviewMissing — suitable for piping into the weekly regen routine (registry trigger trig_012B14fpLS1inAkEuJTZBbnd) which currently encodes this filter in its prompt.

    Closes registry #590 item 6.

Patch Changes

  • ec6a649: Bump @buildinternet/releases-api-types to ^0.2.0. The classification fields (errorSource, errorType, stopReason, retryCount) added by the registry to the Session shape now come straight from the published types, so the CLI's local SessionWithClassification extension is gone. No behavior change.
  • 41b7a95: releases admin overview-write now accepts --unescape-html, which runs a small pre-upload pass to decode &amp;, &lt;, &gt;, &quot;, and &#39;. Useful when the markdown was generated by a sub-agent that escaped entities reflexively.