|
3 | 3 | All notable changes are recorded here and summarized again in the matching |
4 | 4 | GitHub release notes for each tag. |
5 | 5 |
|
| 6 | +## v0.1.9 |
| 7 | + |
| 8 | +- **The GitHub Actions runtime does the work now.** Until this release the |
| 9 | + issue-to-PR loop had never once produced a pull request from Actions, on this |
| 10 | + repository or any other. The engine confines itself with a bundled bubblewrap, |
| 11 | + bubblewrap builds its sandbox from an unprivileged user namespace, and Ubuntu |
| 12 | + 24.04 forbids those by AppArmor policy, so the sandbox died at startup on |
| 13 | + every run: |
| 14 | + |
| 15 | + ``` |
| 16 | + bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted |
| 17 | + ``` |
| 18 | + |
| 19 | + Every command the engine tried then failed, including `pwd`, so it read |
| 20 | + nothing and changed nothing while still exiting successfully. That is why this |
| 21 | + presented for so long as an agent quietly declining to work rather than one |
| 22 | + that had never been able to start. The workflow now enables the kernel feature |
| 23 | + the sandbox is built from, which reads like a weakening and is the reverse: |
| 24 | + with the restriction in place the engine was confined by nothing, because its |
| 25 | + confinement never loaded. Measured on a runner in both directions, same |
| 26 | + binary, only that setting changing. None of the engines' own "dangerous" flags |
| 27 | + are set, here or anywhere. |
| 28 | +- Comment commands answer on the thread instead of in a log nobody opens. |
| 29 | + `@simplycubed-code help` produced the right text and printed it inside the |
| 30 | + runner, so the person who asked saw silence. Worse, `address` on an issue ran |
| 31 | + anyway and failed two layers down with a raw GraphQL error, because nothing |
| 32 | + checked that a pull-request verb had been aimed at a pull request. The agent |
| 33 | + now resolves which surface a comment arrived on, answers with the verb that |
| 34 | + does apply, and stays green: someone using the wrong word is not a failure. A |
| 35 | + comment that merely mentions the agent in passing still says nothing at all. |
| 36 | +- `engine: claude` no longer demands Azure credentials it never uses. The |
| 37 | + adapter was selectable and unusable, because the CLI required an Azure |
| 38 | + endpoint and key whatever engine was chosen, and then wrote a Codex provider |
| 39 | + config the Claude path never reads. Both are now conditional on the engine. |
| 40 | + This is the local CLI path; the reusable workflow still installs only the |
| 41 | + Codex CLI, which is tracked separately. |
| 42 | +- The repository's own comment job installs the commit under test rather than |
| 43 | + the last release, matching the two jobs beside it. It was the one path whose |
| 44 | + regressions could not be caught before they shipped. |
| 45 | + |
6 | 46 | ## v0.1.8 |
7 | 47 |
|
8 | 48 | - **The Actions runtime was dead in `v0.1.7` and is fixed here.** The comment |
|
0 commit comments