Skip to main content

Release 0.1.141

Repave can now run your legacy Windows desktop app and have its agents check scenarios against it. Maintenance projects start from your repository's own feature files and follow its own agent instructions, and a change can wait for a design doc you approve before any code is written.

Upgrade notes​

  • Database migrations run automatically during the upgrade. They add the legacy desktop app, imported feature files, design docs, GitHub issues per change, module pull requests, English module names and the new Daily tests settings.
  • A new image, legacy-desktop, ships with this release. deploy-client-release.sh and the installer add LEGACY_DESKTOP_IMAGE to .env and pull it for you. If you upgrade with scripts/upgrade-client-compose.sh instead, set LEGACY_DESKTOP_IMAGE in .env to this release's legacy-desktop image first; without it the script warns, and legacy desktop apps will not start. On an air-gapped host, docker load the new legacy-desktop archive from the bundle with the others.
  • docker-compose.yml passes LEGACY_DESKTOP_IMAGE to the app. Nothing else to edit.
  • Combined workspaces no longer promote features. A feature whose promotion had failed returns to review when you upgrade; it is delivered through its pull requests from now on.
  • The implementation planning model set in a project's settings moves to the Project implementation plan row of Agent Defaults, unchanged.
  • Hosts behind a VPN or tunnel whose downloads hang inside containers: see "Downloads hang inside containers" in the install guide's Troubleshooting for the one-time Docker setting to apply.

New​

Run your legacy desktop app. Under Tools → Legacy App, drop your 32-bit Windows app (VB6, Delphi and similar) as a zip and give its database connection string; an agent installs it and asks you only for what it cannot work out. For anything else, such as a 64-bit app, build your own image and choose Use my own image. Edit changes the program, login, screen size, connection or image later without setting it up again.

Check scenarios against the legacy app. Verify on legacy app on an As-Is scenario, on a whole feature or on a whole module, has an agent perform each scenario on the real app and report Legacy: Passed, Legacy: Failed or Needs review, with the screens it saw and the database rows it changed. Compare with legacy app on a To-Be scenario runs it on both apps and lists the differences. Where the As-Is does not match what the app did, the run suggests changes you Accept or Reject.

Discover and refine from the running app. Discover with legacy app explores the app and its data before writing the As-Is, and Verify against the legacy app in the Refine dialog checks and fills in an existing one. Every other agent can also open its own copy of the app when it needs to see what it does; there is nothing to switch on.

Legacy screens and Side by side. The screens agents saw are kept under each scenario on a Legacy Screens tab, and Side by side puts a legacy screen next to the new app's story. Prototypes are now designed like-for-like with those screens.

Your repository's feature files become features. In a maintenance project, every .feature file in the BDD Features Path on your base branch appears on the Features page as a merged feature, and changes you push are picked up within about ten minutes. Add feature extends an imported feature instead of making a second one, and implementing it changes only those scenarios in your file.

Repave follows your repository's instructions. In a maintenance project every agent follows your repository's agent instructions file and can use its skills, and your repository wins where the two disagree. Repave never changes that file.

A design doc before implementation. Turn on Write a design doc before implementation under Settings → Implementation (off by default) and every change waits on a design doc on the new Design tab. Approve and implement starts the work; Request changes sends it back.

A GitHub issue for every change. In pull-request mode on GitHub, Repave opens an issue for each change it builds, keeps its status current and closes it when the change merges. A fine-grained token needs Issues: Read and write.

Rename branches, and English names for modules. The pencil on a feature's branch renames it everywhere, your remote included. A module named without Latin letters gets an English name for its branch, which you can set or leave to Repave, and a feature's English name can now be edited.

See the code behind each scenario. After an implementation, each To-Be scenario lists under Code the files and lines that implement it. Click one to read them.

Daily tests run in parallel. Parallel workers runs several scenarios at once, each with its own copy of the app and database, and a daily run has its own memory limit, Daily test run (16 GiB by default). In Repave IDE, /repave:bdd-parallel makes your own test runner support it.

Ask Claude for a feature's scenarios. The Repave connector in Claude can now read a feature's To-Be and As-Is scenarios word for word, and tells you whether it has an approved prototype, with a link to it.

Improvements​

Combined workspaces deliver through pull requests. Test steps, scripts and other files outside every source repository now get a workspace pull request of their own, for features, modules and worktrees alike; merge it last. A module is delivered with Open pull requests. Commits pushed to a combined branch from your own computer are merged in before Push, never overwritten.

A module's page in one view. A module now has five tabs that open where its next step is, one action per stage, a UI Prototype tab showing every member's stories together, and a Preview tab that runs the module's branch. Agents implement members one at a time, so a run that stops keeps every member it finished.

Previews of apps that start their own containers. An app whose dev script starts containers, or that needs a cache, queue or other services from its compose file, now runs in the preview as on a developer's computer. A run-prototype-dev.sh of your own is the one that runs, and Repave no longer copies its own into your repository.

Out of memory says so. A check that runs out of memory is reported as out of memory, with the limit to raise, instead of as failing code. A daily run cut off by memory shows Could not run and starts no fix. A repository script that sets a larger Node heap gets containers big enough for it.

Fewer stored traces. Repave keeps each scenario's latest trace and the ones bug reports point to, and deletes the rest, freeing most of the traces folder on the first start after the upgrade.

Skills page. The Skills page now lists only your project's own skills. Repave's skills keep working for every agent but are no longer shown or edited there.

Storybook projects implement faster. Implementing a Storybook feature no longer takes a screenshot of every story first or re-renders every story before it can finish.

Fixes​

Save & Apply on an untouched agent instructions file emptied it and committed the empty file. The editor now shows the file on disk, and refuses to save over a change made since the page loaded, offering Load current file.

A feature branch already on your remote could lose its implementation there after Repave brought the base branch in. Repave now merges the base into a published branch and never rebases it.

Small PDF documents failed with "Invalid PDF structure" or read the wrong text, for uploaded requirement and rule documents, attachments and templates.

The editor's Source Control view compared a feature branch with the integration branch, so its ahead and behind counts were wrong. It now follows the feature's own branch.

Opening a test trace in Repave IDE also opened a browser tab on your computer.

A Repave IDE session that failed to start showed a command line instead of the reason.

A long question from the assistant pushed the message box out of view.