Skip to content

chore(release): 0.5.0#148

Merged
ThomasK33 merged 1 commit into
mainfrom
release-please--branches--main
Jun 23, 2026
Merged

chore(release): 0.5.0#148
ThomasK33 merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

The next agent-tty release. Merging this PR creates the release tag and GitHub Release and starts the publish pipeline.

[0.5.0] - 2026-06-23

Added

  • Default semantic actions (wait, snapshot, screen hash, batch render-wait, host replay) now use libghostty-vt when the optional native package is installed, with automatic ghostty-web fallback otherwise. Visual artifacts (screenshot, record export --format webm) still default to ghostty-web. Explicit --renderer, AGENT_TTY_RENDERER, and config.json.defaultRenderer overrides keep precedence. (#157)
  • The host now answers terminal capability queries on the live PTY: OSC 10 (foreground), OSC 11 (background), and DSR ESC[5n (status). Eliminates the Neovim 0.12+ E1568 startup warning leaking into captures. Replies are written as child input and are not appended to the event log, so snapshots, screenshots, and recordings are unaffected. (#163)
  • Dashboard: pressing Enter in a maximized view now restores it, mirroring Esc. Footer hint updated to esc/⏎ restore. (#153)
  • CLI exit-code contract documented in docs/USAGE.md (full 011 mapping plus batch fail-fast / --keep-going semantics), with a new top-of-README anchor nav and grouped command-surface table. (#150)

Changed

  • Standalone wait now exits 11 (WAIT_TIMEOUT) on timeout while still emitting the existing ok: true envelope with timedOut: true / matched: false. Makes shell composition fail closed (agent-tty wait … && next-step). Closes #151. (#165)
  • Local-state hardening: the per-session RPC socket directory is now 0o700, the socket file 0o600, and persisted state files (session manifests, Home Registry) 0o600, regardless of umask. The Home and session directories are also locked to 0o700 and events.jsonl to 0o600, so the full terminal byte stream (which can contain secrets) is no longer world-readable. (#158, #161)
  • Snapshot/wait performance: dropped a redundant deep clone of the event log in the libghostty-vt backend and skipped per-event Zod re-validation on the trusted live-host replay path (seq ordering is still enforced). (#161)
  • Dependency audit gate: aube audit --audit-level high now runs in CI; transitive esbuild, vite, ws, and brace-expansion advisories were cleared via package.json overrides. (#158)
  • Pre-1.0 versioning: feat: commits now bump the minor version (e.g. 0.4.x → 0.5.0) instead of being flattened into patches. Breaking changes still bump minor; 1.0.0 remains an explicit Release-As: decision. (#152)

Fixed

  • Dashboard redraws immediately on terminal/tmux pane resize. Previously, panes kept stale geometry for up to ~1.5s on idle sessions; now they track the new size on the first post-resize frame. Also removes a latent NaN-width path on non-TTY stdout. (#162)
  • The standing release-please PR is now opened on release-please--branches--main (the package-name component suffix is gone). (#147)
  • The README status-version badge is now wired into release-please extra-files and bumps with each release PR. (#156)

Docs

  • README tagline mentions agent-browser alongside Playwright. (#155)
  • RELEASE.md support contract reworded to be version-agnostic so release-please bumps no longer stale it. (#158)
  • dogfood-tui skill clarifies when to use live terminal evidence vs source/tests, and that text snapshots are not authoritative for CJK/emoji column-width questions. (#164)

CI

  • PR titles are validated as Conventional Commits via amannn/action-semantic-pull-request, so the squash-merge subject that lands on main always parses cleanly for release-please. (#154)

Maintained by the release-please workflow. Notes are regenerated by Communique on every push to main, so manual edits to this PR are overwritten.

@github-actions github-actions Bot force-pushed the release-please--branches--main branch 2 times, most recently from 0c0feb2 to 4c9515d Compare June 12, 2026 20:43
@github-actions github-actions Bot changed the title chore(release): 0.4.4 chore(release): 0.5.0 Jun 15, 2026
@github-actions github-actions Bot force-pushed the release-please--branches--main branch 11 times, most recently from 1b5f63f to 1420eb4 Compare June 22, 2026 17:01
@github-actions github-actions Bot force-pushed the release-please--branches--main branch from 1420eb4 to 42e8d47 Compare June 23, 2026 12:29
@github-actions github-actions Bot force-pushed the release-please--branches--main branch from 42e8d47 to 7f81d6d Compare June 23, 2026 13:36
@ThomasK33 ThomasK33 added this pull request to the merge queue Jun 23, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 23, 2026
@ThomasK33 ThomasK33 added this pull request to the merge queue Jun 23, 2026
Merged via the queue into main with commit fae02cb Jun 23, 2026
25 checks passed
@ThomasK33 ThomasK33 deleted the release-please--branches--main branch June 23, 2026 13:50
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Decide: should standalone wait exit non-zero on timeout (currently exits 0 with timedOut: true)?

1 participant