Release 0.1.146
A feature, module or worktree can now build on work that has not merged yet, and Repave reads every check on its pull requests and fixes what fails. Repave learning gets its own switch and a Learning page, the home page shows how your projects connect and what a change would affect, and the agent log shows time and can be filtered. Custom workflows and AWS AI-DLC arrive, both off until you turn them on. The test step after you try a feature is now called Write Tests.
Upgrade notes
- Database migrations run automatically during the upgrade. They record custom workflows and their runs, AI-DLC runs, which branches build on which, the checks on Repave's pull requests and the runs that fix them, your projects' database and broker connections and change impact analyses, learning suggestions, more detail in agent logs, and template readings for document types. Every fixed daily test run gets its After fix run listed beside it.
- Repave learning is off on projects that had Apply what Repave learns off. Until now Repave read your repositories and sorted your developers' changes for every project, and the switch only decided whether skills were changed. Now one switch turns learning on or off as a whole, so on those projects Repave stops reading your repositories, and the Learning categories card is hidden. To turn it back on, open Project settings → Context, turn on Learn from your developers' changes, keep Manual review or choose Auto-adopt under When Repave learns something, and Save Changes. Projects that had Apply what Repave learns on keep learning, in Auto-adopt, and what Repave already changed is listed on the Learning page as adopted.
- Rule-aligned batches and scenario sequencing are gone. Implement in rule-aligned batches and
Max scenarios per batch on the Implementation tab, the Scenario Sequencing Model setting, the
Scenario sequencing row in Agent Defaults, and a feature's Implementation Plan tab are
removed, and their saved values are discarded. Every implementation now runs as one agent run over
the feature or the scenarios you chose. The agents commit their own work as they go, after each
scenario and each fix, so a run that stops keeps what it built.
repave project settingsno longer returnsscenarioByScenarioEnabled. - "Awaiting UAT" is now "Awaiting Write Tests". The test step you run after trying a feature is called Write Tests everywhere: the feature status, the Write Tests card in Project settings (was UAT Verification), the module stage, its buttons and dialog, the email digest and the comment Repave adds to a feature's Jira ticket. Features waiting for that step, and their jobs, carry over as they are. UAT Tools and Start UAT keep their names.
- Repave no longer writes a
.mcp.jsoninto your repository. Agents get the browser from the Browser column in Agent Defaults only. A.mcp.jsonyou already committed is left as it is; agents ignore its browser entry, and any other server in it still loads. /repave:scan-reusableis removed. The implementation agents now look for existing code before writing a second copy, and you can ask the same in Repave IDE: what could this branch reuse.- Reading the checks on a pull request needs a token that may read them: a fine-grained GitHub token needs Checks: read, Commit statuses: read and Actions: read, and an Azure DevOps token Build (read). Until then the Checks line says what to grant.
- No changes to
.envordocker-compose.yml.
New
Build on work that hasn't merged. Build on… beside the branch on a feature's page, a module's page or a worktree in Repave IDE makes its branch start from other work still in flight, any number of them. Their new commits come in by themselves within seconds; a running agent pauses, takes them and carries on, told what came in. Chips say what each branch builds on and what holds an update. View stack, and the Stacks tab on the Features page, show a branch's family. A branch merges, or opens its pull request, only after what it builds on has merged. The × on a chip removes a parent and rebuilds the branch without its work.
Stack and deliver automatically, off until you turn it on: Build on the last one started, and deliver when the tests pass in Project settings → Implementation. A feature's or module's first prototype or implementation then builds on the last one started, and once its behavior tests pass, Repave opens its pull request (or merges it) as soon as what it builds on has merged.
Repave fixes failed checks on its pull requests. In pull request mode the Pull Request panel
shows a Checks line for everything your CI reports. While CI runs, Repave reads it every minute; when
a check fails, a timed-out job included, an agent reproduces it with the job's own command and fixes it,
together with anything SonarCloud's quality gate found. Before leaving a failure the branch did not cause,
it asks you: Fix it or Leave it. Fix again starts another run, with an optional instruction.
Checks are read on single-repository projects, on GitHub, Azure DevOps and Team Foundation Server.
repave pr checks lists a pull request's checks, or prints one check's whole log.
A worktree's pull request is fixed like a feature's. Its row in Repave IDE shows its Checks and SonarCloud lines; Repave fixes what fails, resolves a conflict with main first, and addresses review comments with Address N comments, always leaving your uncommitted edits as they are and pushing only its own commit. On a combined workspace, SonarCloud takes a Project key per repository.
Stage a worktree. A worktree's row in Repave IDE has Stage, like a feature's page. A worktree you cut yourself in a terminal is listed too, marked made outside Repave, with the same actions.
The Learning page. Learning, in the Management menu, lists what Repave learned from your developers' changes and what it suggests: an edited skill, a new skill or a new validation rule. Adopt, Edit, Reject or Undo each one; the number beside the menu entry counts those waiting. In Auto-adopt, Repave adopts them itself.
See how your projects connect, and what a change affects. The home page's Map tab draws your projects, the APIs they call of each other, and the databases and message brokers they share. Change impact, under Analysis, takes a change described in plain English and reports, for this project and every project that depends on it, whether each place Breaks, Needs a check or is Not affected, with the scenarios to re-run and what the analysis could not see.
Custom workflows, off until you turn them on: Allow custom workflows in this project in Project settings → General. Workflows, under Management, then lets you draw a process of your own of agents, checks and decisions, describe one in words for Repave to draft, try it with a test run, publish and run it.
Run the pipeline with AWS AI-DLC, off until you turn it on in Project settings, on web application projects. From Requirements then becomes Start with AI-DLC, which runs AI-DLC's own stages in a chat and asks you at each one before moving on; when it completes, Repave takes over each feature or module.
Choose what Write Tests covers on a module. Write Tests on a module opens Write Tests for module, where you pick the features, the model and instructions for the agent. While it runs, the module reads Verifying.
Improvements
The agent log shows time and can be narrowed. Each entry shows when it happened, and a wait over 10 seconds shows how long. A sub-agent's work is grouped under its task. The bar above the log filters by All, Bash, Files, Search, MCP or Errors, or by text in Filter log…, and says Showing N of M entries. While a job runs, a Running strip names the tool in use.
SonarCloud fixes cover everything that fails the gate: every bug, vulnerability or code smell the failing rating counts, duplicated blocks and security hotspots that are a real risk. Repave asks you before it leaves any finding unfixed.
Pull Requests page. A module's pull request is one row, named for the module. The Repave column, which replaces Comments, says what Repave is doing or waiting for on each pull request; click it to see the pull request's details.
Every agent asks before changing a scenario. The agents writing the code or tests, the legacy behaviour review and validation rule checks now ask you, as the code review did, and you are asked only once per run.
Agents reuse existing code instead of writing a second copy of a helper, service or wrapper your project already has.
Templates for document types. An agent reads an uploaded template or example into one box, What Repave took from it: its cover, contents, end page, header and footer, then an outline of sections. Edit it like any text.
A daily test run whose suite could not start can be fixed. It reads Failed with The suite could not start., View runner log opens the runner's log, and Fix failures works as for any run. The suite a fix ran is now its own run, After fix.
⌘B on a Mac, Ctrl+B elsewhere collapses and expands the project side menu.
Repave learning can tune the agents' own procedures for your project, the steps each implementation agent follows on every run.
Smaller touches. Compare code's file buttons show the file name, with enough of its folders to tell
two same-named files apart. A module's agent conversations, and the runs fixing its pull request, are
titled with the module's name. repave pr status prints each pull request's Checks and
SonarCloud lines, for a worktree's too.
Fixes
- A module's page could show a feature's old branch instead of the module's, and Push then published the wrong one.
- A bug fix or revision could be failed after its review passed, and its work lost, when the agent described its changed files in words.
- An edit typed into the agent instructions on the Context tab while Project settings was still loading was lost on Save & Apply.
- Write Tests could fail a feature whose tests had all passed, because the agent mistyped a scenario's name.
- A module run could leave a finished feature's work uncommitted, and the branch's chip then waited "when this run finishes" with nothing running.
- Two scenarios with the same title under different rules became one scenario twice in a new feature file, and the file was refused.
- Agents tried to download a browser for Playwright, which cannot work in Repave, when a test said its browser was missing; they now use the one already installed.