Skip to content
Wakeplane

v0.3.0-beta.1

This beta refresh packages the Postgres backend, optional bearer auth, request audit, bounded receipts, retention, schedule export/import, and operator console added after the March beta. It adds assistant access and complete external automation paths.

  • MCP assistant tools share the REST application’s authentication, audit, validation, and durable execution boundary.
  • Guided schedule creation/editing includes paused defaults, recipes, explicit timezones, timing previews, policy, and retry controls.
  • Asynchronous HTTP jobs track durable remote identity, progress, results, and artifacts through completion and restart recovery.
  • Event delivery creates one occurrence per schedule/source/event identity; conflicting replay is rejected and deduplication survives run pruning.
  • Repository-watch and weekly reading-list recipes demonstrate a separate runner with optional webhook notification.
  • Empty or host-dependent timezones and overflowing durations are rejected. Cron start windows and impossible dates are handled explicitly.
  • CI and release gates include Go vet, race tests, real Postgres integration, generated docs, JavaScript lint/format, and console tests. Archive smoke checks require the embedded binary version to match the release tag.

Compatibility and upgrades

Section titled “Compatibility and upgrades”

Existing cron/interval/once schedules and plain HTTP/shell/workflow targets retain their contracts. External tracking is an opt-in target.http_job object. New additive tables store external checkpoints and event identities; migrations repeat safely on SQLite and Postgres. Back up the database before upgrading. Older binaries do not understand the new tracking mode; preserve an older-version backup for rollback rather than executing tracked targets with an older binary.

This remains pre-stable and intended for a single operator on trusted infrastructure. RBAC, multi-tenancy, OAuth account connection, provider spending enforcement, distributed coordination, and remote cancellation are not included. Agent and connector behavior stays outside the core. Runner idempotency is required; local run identity alone does not guarantee exactly-once external side effects.

Source documentation identifies the version being built. Release availability is confirmed by a matching tag and downloadable archives on GitHub Releases.