Skip to main content

Release 0.1.150

Autopilot takes your ready features through implementation, tests and pull requests, a few at a time, until they merge. It replaces the implementation plan. Resuming a run now finishes what the run was for.

Upgrade notes​

  • Three database migrations run on upgrade. They cancel any implementation plan still in progress; the plan and its settings are removed.
  • NEXT_PUBLIC_ENABLE_IMPLEMENTATION_CONDUCTOR is no longer used; you can delete it from .env.
  • No changes to docker-compose.yml.

New​

Autopilot. With automatic stacking and UAT-first on, Autopilot has its own item in the side menu under Develop Features. Put ready features in its bucket — every scenario approved and a UI prototype — from the page, or select them on Discover or Develop and choose Add to Autopilot. Start Autopilot builds them At a time (3 by default): each is implemented, its tests are written and its pull request opened, and when one merges the next starts. When it cannot settle something, the feature shows Needs you with one-click answers. Stop new starts lets the features already going finish. A module member goes through Autopilot on its own branch and pull request. The Plan tab and Implement All are gone.

Improvements​

  • Resume on a failed, timed-out or cancelled run now finishes its work: a fix to a pull request updates the pull request, and a review run posts its replies. If a newer run has taken over, Resume says so. A run that cannot be carried on no longer offers Resume.
  • When an agent asks to remove a scenario and you say Yes, a module member is no longer left Partially Implemented because of the removed scenario.

Fixes​

  • An HTML prototype run could fail when a feature it builds on changed.
  • A module run could refuse to publish a member's scenarios at the end of the run, after repairing them itself.
  • The assistant and the Repave IDE could report a feature's To-Be as done before one had been generated.