Skip to main content

Release 0.1.149

The top-bar search now finds modules and individual settings, and you can correct a detected unit test suite's commands in Settings. Agents that change your code also run the static checks your CI runs.

Upgrade notes​

  • No database migrations.
  • No changes to .env or docker-compose.yml.

New​

Search finds modules and settings. The search box in the top bar (⌘K or Ctrl+K) now lists Settings and Modules alongside Pages and Features. Choosing a setting opens its tab of the Settings page, scrolled into view, with the cursor in it. A setting that appears only after another one is changed, such as SonarCloud, takes you to the setting that reveals it, with a note saying so. Pressing / no longer opens the search.

Correct a detected test suite. In Project settings → Implementation → Unit Test Configuration, choose Edit on a suite to change its working directory, test command, coverage command, coverage report and format. Repave saves what you type without running the suite and marks it Not verified; a command that does not work fails at the next unit test check, with the reason. Re-detect Test Suites replaces your changes.

Improvements​

Agents run your CI's checks before finishing. Every agent that changes your project's code — implementation, fixes, prototypes, Write Tests, merges and characterization tests — now leaves the branch lint-clean, and also runs the static checks your CI definition runs, such as format checks and code scans. It runs every check rather than stopping at the first failure.

Fixes​

  • In an agent conversation, Scroll to bottom did nothing while a tool was running, and the button sat against the scrollbar.