Skip to main content

Release 0.1.142

Staging replaces Bundles: stage features and modules together on one branch and run them side by side before anything is delivered. Discovery now tells your organisation's own systems apart from third parties' and links them to the Repave projects that own their code, and every implementation ends with a code review.

Upgrade notes​

  • Database migrations run automatically during the upgrade. They add staging, internal systems, As-Is versions, module build order, the code review and per-feature documents.
  • Bundles are removed. Existing bundles are removed when you upgrade; stage the features again from their pages if you still want them together.
  • Check DATABASE_URL if you changed it. The app now refuses to start if DATABASE_URL carries an sslmode other than disable, any other ssl… setting, schema, connect_timeout, socket_timeout, pgbouncer or statement_cache_size, and names the one it found. The DATABASE_URL in the released docker-compose.yml has none of these.
  • New optional setting DATABASE_CONNECTION_LIMIT in .env: how many Postgres connections the app opens, 20 by default. Raise it only if the app logs timeouts waiting for a database connection; Postgres allows 300 in all.

New​

Staging. Stage on a feature's or module's page merges its branch, finished or not, into one shared staging branch (repave-staging, renameable under Project Settings → Integrations → Staging branch). If it conflicts with what is already staged, an agent resolves the conflict on the staging branch. The fix is kept only if the build passes. If it can't, staging stays as it was and you get Retry. The Staging page lists what is staged and marks New commits. It runs the staged app in the inline browser and offers Update from main and Reset staging. Staging never changes your feature or module branches.

Internal Systems. Discovery now lists your organisation's own systems, such as core banking or a shared login service, under Internal Systems, apart from third-party External Systems. When the code doesn't settle who owns a system, it asks you instead of guessing. When an internal system's code is another Repave project, the two are linked. After that, each call names the exact API it uses, scenarios cite those APIs, and implementation builds against that project's real contracts.

Modules build in order. A module's Features tab numbers its features in the order they will be built, with a line for each dependency. Every run on the module follows that order, and the agent asks you when it can't tell which comes first.

Implement module brings your features' work over. Work a feature already had, on its own branch, uncommitted or pushed from outside Repave, is merged onto the module's branch as the run's first step. An agent resolves conflicts and asks you when the two sides genuinely disagree.

A code review after every implementation. Once the other checks pass, a review looks for bugs they can't see, such as a crash, lost data or a missing permission check, and the agent fixes them. The Implementation pane says what was fixed. When the review thinks a scenario is wrong or missing, it asks you, and a Yes adds it to the To-Be and implements it in the same run. Write tests now runs the same review once the tests pass.

Documents per feature, in the format you need. A document type can now be written for each feature, from that feature's Documents tab, and is updated after each implementation of it. Each type chooses its format (HTML, PDF, Word or Markdown) and where it goes. It can stay in Repave, or be committed into your codebase at a path you set, on the feature's or module's branch, with a link to that branch.

Improvements​

Stories follow a changed To-Be. When a feature's To-Be changes after its stories were written, the Stories segment says which scenarios no longer match, and Update stories brings them in line.

The module page's header shows the module's branch with Push, Pull and rename, as a feature's page does, plus a link back and Start UAT. The running-agents list names the module a run belongs to.

Scenario cards show their id, such as TOBE-012 or ASIS-007, beside their number, so you can quote it and find it in Mapping.

Earlier versions of the As-Is are kept whenever discovery, refinement or an edit changes it, and updating a feature from the command line keeps its As-Is scenario ids.

Storybook prototypes now work with Angular 14 frontends. A frontend with a Storybook older than 7 is told to upgrade it first.

A fixed Daily tests run's PDF report shows only the result after the fix, on the commit the fix was merged as. The first run stays on the run's page.

Fixes​

spring init failed in agent runs with a missing-class error, so new Spring Boot projects could not be generated.

Resuming a chat whose agent session was deleted failed. It now starts a fresh session.

A link that opened a new tab in the inline browser could send your next click to the wrong tab.

Prompt History's context filter offered contexts with no prompts.

repave write-as-is-gherkin --dry-run against an older Repave saved the As-Is anyway without saying so; it now fails, saying the As-Is was saved.