Skip to content

Portal v0.27.0 — Reliable runner startup and clearer MCP failures

Choose a tag to compare

View all tags
@AndrewDryga AndrewDryga released this 16 Jul 10:28
· 1995 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.27.0
This tag was signed with the committer’s verified signature.
AndrewDryga Andrew Dryga
GPG key ID: 73B7DDE1A8AC23B9
Verified
Learn about vigilant mode.
1ff3c73
This commit was signed with the committer’s verified signature.
AndrewDryga Andrew Dryga
GPG key ID: 73B7DDE1A8AC23B9
Verified
Learn about vigilant mode.

Runner v0.12.0 closes the startup and failure-reporting gaps found during pre-1 certification. The portal also makes MCP failures and connector setup clearer without requiring a new MCP bridge binary.

Upgrade note

Upgrade each runner directly to runner-v0.12.0 during a maintenance window with no pending dispatches. This release starts the final durable dispatch journal and does not import older unacknowledged entries. Once v0.12.0 writes new dispatch records, downgrading to an earlier runner is unsupported.

The MCP bridge remains mcp-v0.3.0.

Runner

  • Unsigned installations no longer open or lock signing nonce state during startup.
  • Corrupt durable dispatch state stops the runner before it connects to the control plane.
  • Failure causes redact sensitive action arguments before they reach local audit records or the portal.

MCP and connectors

  • MCP run summaries include a bounded terminal failure message when the runner provides one.
  • OAuth consent lets a person choose which account to connect.
  • Key-bearing connector commands avoid being stored in shell history.

Delivery

  • A newer non-destructive production plan supersedes an older pending plan. Terraform confirmation remains the single human apply gate.
Assets 3
Loading