Release v0.28.0 - #496
Conversation
de6fe44 to
9909366
Compare
9909366 to
d711210
Compare
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d71121061b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - **Auto permission mode** (#494) — a new stop between AcceptEdits and Allow in the Shift+Tab cycle: provably-harmless operations (read-only tools, allowlisted read-only shell commands) run without prompting while everything else still asks. Protected-path and destructive-command guards run first, unchanged. | ||
| - **Tool events on `serve` carry input and output** (#488) — `tool_start` now includes the tool's arguments and `tool_result` its content (capped at 64 KiB), so SSE/WebSocket consumers can render the bash command, the edited file, or the unified diff. Both fields are additive; existing consumers are unaffected. | ||
| - **Live session dashboard in the Flutter client** (#486) — the session list shows per-session activity (working / needs input / idle) derived from each session's own event stream, with a summary header across sessions. | ||
| - **`@path` file mentions restored in the TUI** (#493) — gitignore-aware Tab completion under the cursor, contents inlined on submit (transcript keeps the literal line), directories expand to a one-level listing; queued and interjected prompts expand too. This had regressed out with the classic REPL removal. |
There was a problem hiding this comment.
The post-v0.27.0 history also includes #499 (46dd5df), which fixes @path tags to use forward slashes on Windows, but this release entry only describes the original #493 restoration. Consequently, the 0.28.0 changelog omits a shipped, user-facing cross-platform fix; include #499 under Fixed or incorporate it into this bullet.
AGENTS.md reference: AGENTS.md:L174-L180
Useful? React with 👍 / 👎.
|
Codex Review: Didn't find any major issues. Can't wait for the next one! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
emal-avala
added
run-e2e
The Windows forward-slash fix for @ mention labels shipped after the section was stamped and was missing from the release notes.
143e059 to
219c01c
Compare
1 participant
Summary
Cuts v0.28.0. Bumps
crates/lib,crates/cli,crates/eval(path-dep only),Cargo.lock, andnpm/package.jsonfrom 0.27.0 -> 0.28.0. Stamps the CHANGELOG with the changes merged since the v0.27.0 release.Highlights
Auto permission mode (#494):
Shell classification hardening (#495):
env,nice), quoting, and subshells can no longer disguise a mutating command as read-only. Closes a bypass of the destructive-command warning.Serve API: tool detail streaming (#488):
tool_startevents carry the tool's input andtool_resultits output (64 KiB cap) on SSE/WebSocket — enough for GUI clients to render commands, file paths, and unified diffs. Additive fields; existing consumers unaffected.TUI restorations and fixes (#490, #492, #493, #489):
@pathfile mentions are back (gitignore-aware completion + inline expansion), user turns are tinted in the transcript, Ctrl+L repaint / kitty keyboard push / desktop notifications are actually wired up, and the accessibility themes (colorblind + ANSI-16) dropped by the 0.27.0 theme rewrite are restored with guard tests.Flutter client dashboard (#486) and release-pipeline npm fix (#487) round out the release. The #487 fix takes effect for this tag: it pins the npm publish job to node 24 + npm ^12, which is what broke the v0.27.0 npm publish.
Full changelog is in
CHANGELOG.mdunder the[0.28.0]heading.Verification (RELEASING.md section 4)
run-e2elabel addedcargo check --all-targetscargo test --all-targets(local: only the 3 known environmentalbwrap_*sandbox failures on this host)cargo clippy --all-targets -- -D warningscargo fmt --all -- --checkrun-e2eworkflow passedAfter merge
Follow RELEASING.md section 7: tag
v0.28.0on main and push. Release automation handles Linux/macOS/Windows binaries, crates.io publish, npm publish, Docker image publish, and Homebrew tap update.CARGO_REGISTRY_TOKEN(v0.27.0 crates.io publish failed with 403) and fixHOMEBREW_TAP_TOKENpermissions (contents:writeon avala-ai/homebrew-tap) — otherwise those two publish jobs fail again. The npm job is fixed by ci(release): pin npm publish job to node 24 + npm ^12 #487, which is included in this release.