Skip to content

AgentGit v0.3.0-beta.7

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 29 Oct 21:18
· 5 commits to main since this release
2ad7308

Upgrade: metadata schema 8 and control schema are unchanged from beta.6. Back up before upgrading. Returning to beta.5 or older requires the pre-upgrade backup.

Fixed

  • Enforce credential stream restrictions for proposal reviews, discussions, workspace mutations, validation scheduling and queue admission, including requests that name a proposal or workspace instead of a stream (#124).
  • Serialize garbage collection with metadata root changes and validate newly retained history before committing it. Pins, publication and workspace roots cannot acknowledge objects swept by a concurrent collector; backups use the same lock order (#130).
  • Compare workspace head/base in the committing transaction and preserve the winner of concurrent modifications and syncs (#129).
  • Reject a close that loses a race with proposal integration, preserving its integrated terminal state (#131).
  • Create a workspace at its requested starting revision atomically; invalid revisions leave no workspace behind (#125).
  • Preserve UTF-8 BOM bytes and uniform CRLF line endings when editing or renaming files in the browser, including textarea normalization (#123).
  • Include old/new Git modes and explicit per-file truncation in API/Web diffs; bound both diff input and generated patch bytes (#127, #128).
  • Align security support, release and schema documentation with the current beta and check these statements for drift (#126).

Improved

  • Published release checks install from the public, version-pinned download URL on clean Linux and macOS runners, verify checksum and provenance, and exercise the installed binaries end to end.

Added

  • The Web UI has a shared, restrained visual system across the work queue, repository list and overview: readable controls, sentence-case table headers, semantic status icons and a consolidated summary strip. Existing routes, URL filters, permissions and light/dark modes are retained.

  • Task details show admitted attempts and let the creator change the attempt limit before execution, or an operator afterwards. Confirmation preserves the inspected limit; conflicting edits retain the draft. Existing task instructions and run history stay unchanged.