17a072c924
- Add cloudflared install/detection support in remote settings API, UI, and route tests - Surface Cloudflare tunnel prerequisites in Settings modal with remote access docs updates - Harden heartbeat runtime scheduling by avoiding stale timeout state and simplifying runtime timeout handling - Expand CLI/core/dashboard/engine coverage for task lifecycle, agent health, and runtime heartbeat behavior - Add changesets for heartbeat scheduling fixes and PR approval setting updates Fusion-Task-Id: FN-2920
1.1 KiB
@runfusion/fusion, runfusion.ai, @fusion/core, @fusion/dashboard, @fusion/desktop, @fusion/engine, @fusion/mobile, @fusion/pi-claude-cli, @fusion/plugin-sdk
| @runfusion/fusion | runfusion.ai | @fusion/core | @fusion/dashboard | @fusion/desktop | @fusion/engine | @fusion/mobile | @fusion/pi-claude-cli | @fusion/plugin-sdk |
|---|---|---|---|---|---|---|---|---|
| minor | minor | minor | minor | minor | minor | minor | minor | minor |
Add requirePrApproval setting (related to #21).
When mergeStrategy: "pull-request", GitHub's required: true flag for status checks only flows from branch protection — a Pro feature on private repos. On free private repos, isPrMergeReady reports every fresh PR as immediately mergeable, so autoMerge: true causes Fusion to auto-squash-merge the moment the PR opens with no chance for a human to review it.
The new requirePrApproval setting (project-level, default false) makes Fusion hold the merge until at least one approving GitHub review is present (reviewDecision === "APPROVED"), independent of GitHub's server-side enforcement. Surfaces in the dashboard's Merge settings panel under the Pull Request strategy. Lets you use Fusion's PR mode as "open the PR, wait for me to approve and merge" on any tier.