Repository navigation
1.2.7: clean up after the pipeline, see more dependencies
Built from a heavy user's report: 461 agent runs, about $632, every feature of their last release built through the pipeline.
| Problem they hit | What 1.2.7 does |
|---|---|
169 agent/issue-N branches on the remote, 114 local, 83 worktrees, left behind after merges |
agent-flow clean previews first and removes only with --yes. It touches only agent/issue-N, and only when the work is provably merged (tip is in the default branch, or equals the head of a merged PR, squash merges via gh). Never uncommitted work, never an issue with a run or decision still open. Each delete is checked against the commit it judged, so a push that landed after the preview is kept. |
state dismiss --merged left the worktrees and branches |
--clean removes them too, with the same checks. |
| A new database image or Python dev dependency reached review unseen | Risk review now reads poetry groups, PEP 735 [dependency-groups], uv dev-dependencies, requirements/*.txt, constraints*.txt, Pipfile, and base images in a Dockerfile or compose file. |
| A push blocked by GitHub secret scanning said almost nothing | The message names the file, says to build a fixture's fake secret at run time, and gives the URL to allow it. Other repository rules keep their own message. |
| QA re-ran what the gates had just run | QA reuses a passing gate run when it would run the same commands, so the QA role is not launched. One trial run on a real repo took 18 min and $0.68, against 63 min and $1.23 for a comparable run before. pipeline.qa_reuses_gates: false turns it off. |
| New tests that no gate ran passed unnoticed | The final summary lists them (not_gated). |
| Runs killed mid-way by a 30-minute background limit | The orchestrator skill says a run takes one to two hours and how to resume (npx @drix10/agent-flow run <issue>). |
When you update
Dependencies that were invisible before can now show up as new in agent-flow audit-risk --fail-on-new, once. A base image looks like dependency:Dockerfile:image:node. Review the list, then run agent-flow baseline accept --all --yes. A Dockerfile or compose edit is also a medium-risk change now.
Tested
522 tests on Windows (520 passed, 2 skipped) and on Linux (521 passed, 1 skipped), 0 failed. CI is green on Ubuntu, macOS and Windows with Node 20 and 22.
Full list: CHANGELOG