Paseo Hub v0.11.0

0.11.0 - 2026-10-25

Added

• One trigger can run on a schedule and on demand: schedule.tick may share a document with other events such as manual.run, so a prompt no longer needs two files. A tick runs with each input's default, so a document with a schedule cannot declare a required input.
• run.background: true creates a Paseo background workspace for a run, keeping automated runs out of ordinary workspace listings. It defaults to false; daemons without background workspace support ignore it and run visibly.
• An unverified user who signs in with the correct password receives a verification email immediately, and the link signs them in.

Changed

• CLI logins authorize only while their creator is still an owner or admin of the organization; removing or demoting a member revokes their CLI credentials. Organization API keys and enrolled daemons are unaffected.
• Connecting a GitHub installation now requires the GitHub account owner, or an active admin of the organization that owns the installation. The GitHub App needs the Members read-only organization permission; an existing App must have it approved on the installation before reconnecting.
• Connecting a GitHub App discovers its complete repository catalog before reporting success, and installation webhooks keep the catalog current, so a trigger with filters.repo resolves repositories on a newly connected installation.
• Tables size each column by its widest value; only columns whose values can be cut share the remaining width.

Fixed

• Every run of a trigger with several events carries the trigger's name, instead of an internal event name, in workspace titles and on the home page.
• Background runs receive agent status updates, so Hub observes completion, enforces the idle timeout, and archives the workspace instead of leaving cleanup pending.
• A run with auto_archive: true whose agent went idle during a Hub restart, reconnect, or deploy is archived after recovery instead of staying open indefinitely.
• GitHub notifications for a deleted comment or an uninstalled App settle instead of retrying every 30 seconds.
• When a background refresh of a loaded Hub screen fails, the screen keeps its last loaded content and retries instead of replacing it with an error.