Release 0.1.144
An agent now writes the title and description of every pull request you open, and Repave can read SonarCloud's quality gate on its pull requests and fix what fails. A feature whose checks still found something when their review rounds ran out says so until someone resolves it. Daily test runs test what is merged in your repository, and each fix works on a branch you can pick up. Agents drive the legacy app without stopping for approvals, and a project's keys and tokens no longer leave Project Settings, in the browser or in a backup.
Upgrade notes
- Database migrations run automatically during the upgrade. They add the SonarCloud connection, implementation warnings on features, the pull request writer's saved descriptions, and each daily test fix's branch.
- SonarCloud needs internet access to sonarcloud.io. An air-gapped installation cannot connect it; nothing changes until a project does.
- A backup made before this release restores without its keys and tokens. After restoring a project, enter its API keys, tokens and registry passwords again in Project Settings.
- No changes to
.envordocker-compose.yml.
New
An agent writes your pull requests. Create PR and Refresh PR now have the Pull request writer agent read the change and write the pull request's title and description: what the change does, the files it touches, how it was validated and the issue it closes. The title starts with the feature's Jira key or GitHub issue. Refresh PR rewrites them only when the code, or what was validated, has changed. If the writer cannot finish, nothing is opened or updated and the job says why; press the button again. Its model and timeout are in Settings → Agent Defaults.
SonarCloud on your pull requests. In a project that merges through pull requests, Settings → Integrations → SonarCloud connects the SonarCloud project that analyses your repository: enter its Project key and a Token with Browse permission. Each feature's pull request panel then shows the quality gate: Analysing, Quality gate passed, or Quality gate failed with each failed condition. When the gate fails, Repave fixes it by itself: an agent fixes the issues and writes unit tests for uncovered new lines, and the pull request is updated. Repave never weakens a test or excludes code to pass the gate; a finding it judges a false positive is declined with its reason and listed on the panel. Security hotspots are left for you to review in SonarCloud.
Implemented with warnings. When the legacy behaviour review, the UI check, the code review or the database schema check still found something after the project's review rounds ran out, the feature reads Implemented with warnings, in amber, and its Implementation pane lists what each check still found. Fix them in Repave IDE or your own IDE, then click Mark resolved: the feature reads Implemented, and Repave records who resolved them. Mark resolved needs the Editor role.
Daily test fixes on branches of their own. Every fix a daily test run starts works on a branch of its own, in a worktree listed in Repave IDE. The run's Fix card shows it with the same actions: Open in Repave IDE, Push, Create PR (or Merge to your base branch) and Pull. A fix that does not land keeps its changes on that branch, so you can push it, open a pull request from it, or carry on in Repave IDE. A later fix's pull request says which earlier one it replaces. An earlier fix branch nobody used is removed when the next fix starts.
Improvements
Daily test runs test what is merged in your repository. Before the suite starts, a run brings the project's branch up to date with your repository, including changes merged outside Repave. If it cannot, the run reads Could not run and says why, instead of testing old code.
Agents drive the legacy app without asking for approval. Clicking, typing (signing in with the test login included), setup commands and queries on the legacy app's database no longer wait for an approval in the agent chat. Verify on legacy app could previously stop at the sign-in screen waiting for one.
Verify on legacy app uses the Pro tier by default. Verifying a scenario, a feature or a module on the legacy app now runs on the Pro model unless your project has chosen its own model for it. Setting up the legacy app and Compare stay on Elite.
Project keys and tokens stay in Project Settings. Opening a project no longer sends its API keys and tokens to the browser, for any role. A Viewer can no longer change the project's target stack.
Backups leave out keys and tokens. Create Backup no longer includes the project's API keys, tokens, Repave IDE environment variables, repository tokens or registry passwords, nor anything its members have outside the project. The Project Backup card says so.
Fixes
- After the To-Be was regenerated, a feature's file could keep the old scenarios beside the new ones, and publishing it failed on every later run. The file is now rebuilt from the To-Be.
- A project whose test runner changes into its own test folder could have a passing run reported as missing every scenario, and a feature-branch update thrown away. The suite is now read from the folder where its Cucumber configuration lives.
- A long BDD run started by an agent could be cut off after half an hour and leave its test stack running, blocking the next run.
- Agent runs late in a long job could fail because the project's skills were no longer available.
- Each Save under Settings → Integrations added another Issue tracker card to the page.