Skip to content
Wakeplane

v0.3.0-beta.2

This beta improves crash recovery and makes Discord and Gmail delivery available in the separate automation runner. It also adds packaging for a private, single-operator hosted trial.

  • Ordinary expired-running-lease recovery commits the failed outcome, retry or dead letter, and lease removal in one transaction on SQLite and Postgres. A renewed lease fences stale recovery; failed follow-up writes roll back the entire recovery.
  • New execution leases start at claim time, so slow candidate discovery or policy checks cannot consume the lease before execution starts.
  • Native Discord delivery uses a configured webhook, disables mentions, bounds content, and records the confirmed provider message ID.
  • Gmail delivery uses a separately provisioned offline OAuth grant, refreshes access tokens, and records the confirmed provider message ID. Assistant-connected Gmail credentials are not runner credentials.
  • Ambiguous native sends remain visibly unconfirmed and are not automatically resent. Collection success is separate from delivery acceptance or inbox placement.
  • Paused repository-watch/Discord and weekly-digest/email recipes keep credentials on the runner.
  • Every platform archive now includes automation-runner alongside wakeplane and wakeplaned. The hosted installer continues installing the CLI and daemon.
  • Non-root Docker packaging, Railway daemon/runner configuration, and platform PORT support enable a private deployment trial. CI verifies image build, authentication, and persistent restart behavior.

Compatibility and upgrades

Section titled “Compatibility and upgrades”

Existing CLI, REST, MCP, schedule, and typed-target contracts remain unchanged. This increment adds no storage migrations. Native notifications are opt-in; generic webhook delivery retains its existing idempotency contract. Each runner job selects one channel. Stop the old daemon before replacing it and preserve both database backups and the separate runner state directory. Do not run multiple daemon or runner replicas.

Verification boundaries

Section titled “Verification boundaries”

Go vet, race tests, real Postgres integration, formatting/lint, console tests, generated docs, container checks, and archive smoke checks gate this release. Provider fixture tests establish adapter behavior; they do not establish a live OAuth grant, real Discord receipt, inbox placement, or hosted production observation. A Gmail connector connectivity check does not validate the unattended runner.

Wakeplane remains public beta for a single operator on trusted infrastructure. A hosted trial and sustained workload evidence are still needed before a stable release. RBAC, multi-tenancy, OAuth account onboarding, provider budgets, distributed coordination, and remote cancellation remain outside this release.