Release 0.1.143
Features can now be linked to Jira tickets, open feature branches keep up with your base branch on their own, and the Repave IDE can run your project's own test stack the way agents do. The automatic accessibility checks are removed; the preview's Accessibility button stays.
Upgrade notes
- Database migrations run automatically during the upgrade. They add Jira links, who approved each scenario, and the Repave IDE's mounted files and environment variables.
- The automatic accessibility checks' settings and saved results are removed by the upgrade.
- Open Repave IDE sessions end when you upgrade. The editor now listens on a different port inside the session, so a session started before the upgrade is stopped and the next open starts a new one. Files on disk are kept; open terminals end.
- No changes to
.envordocker-compose.yml.
New
Jira tickets for features. Settings → Integrations → Issue tracker now offers GitHub Issues (the default), Jira or None. With Jira, each feature is linked to a ticket, from the feature's header, the Repave CLI or a CSV import, or Repave creates one. Repave comments on the ticket when the To-Be scenarios or the design are approved, when the feature is implemented, and when its pull request opens and merges. Branch names, commit messages and pull request titles carry the ticket's key.
Feature branches stay current on their own. When the base branch moves, Repave updates the open feature branches by itself, usually within ten minutes, exactly as Update feature branches does. A branch in use is updated once it is free. A conflict the agent could not resolve is not retried on its own; it stays marked Conflict: needs attention until someone resolves it.
Compare code on a Mapping row. A row whose As-Is scenarios point at legacy code and whose To-Be scenarios point at the new code has Compare code: the legacy code and the new code side by side, opened at the lines the scenarios cite, with Full file to read the rest.
Repave IDE: mounted files and environment variables, and port 8080 is free. The Repave IDE card in Project Settings has two new boxes. Mounted files puts files or folders from the server into every session, read-only. Environment variables sets variables in every session. A test script that needs a file from the server, or a variable set before it runs, now runs in the IDE as it does for an agent. The editor no longer uses port 8080 inside the session, so your application can.
Choose what Verify on legacy app checks. Once some of a module's As-Is scenarios have a result, Verify on legacy app asks whether to verify everything that hasn't passed, only what hasn't been verified yet, or everything again.
Filter Legacy Screens and Side by side by status. A row above each list offers All, Passed, Needs review, Failed and Not verified, with counts. Your choice is remembered for the page.
The Approved badge says who approved. A To-Be scenario's Approved badge names the person who approved it and opens its version history.
Improvements
Unit tests must cover what the feature changed. The unit-test check used to look only at the whole project's coverage, so a feature could add code with almost no tests and still pass. It now also checks the lines the feature added or changed, and the agent is sent back to test the files it missed.
Repave learning writes broader lessons. A lesson learned from your corrections now covers the kind of code they were about, such as the same data access or the same control, not just the screens where you made them.
Running agents name the module for a module's Verify, build-order and work-merge runs, instead of the project.
The accessibility checks that ran on their own are gone. Implementation and prototypes no longer run an automatic accessibility check, and its card is gone from Project Settings → Implementation. The preview's Accessibility button still checks the screen you are on. The target-stack design check moves into the Prototypes card, under Also build selected designs on the target stack.
Fixes
- A feature whose tests ended green could show 0 of N passed as its only test run. The test results now show the last run of the implementation, not the check made before any code was written.
- An agent run that waited overnight for your answer failed every Repave command with "Unauthorized" when it resumed. It now keeps working until its job ends.