Skip to content

v0.3.0 - Agent workflows

Choose a tag to compare

View all tags
@sandeepshelke sandeepshelke released this 10 Oct 14:30
v0.3.0
cc7c956
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

gitpro v0.3.0

Built from merged main commit cc7c956d53908ac8bdce6611845a0da59a0d768c (PR #2).

Highlights

  • Preview-first CLI behavior, with existing explicit execution flags.
  • Versioned CLI/MCP preflight and scoped commit, push, and GitHub PR operations.
  • Durable idempotency, cooperative locks, and read-only reconciliation of uncertain outcomes.
  • Exact persistent-change proposals, human approval or narrowly scoped operator policies, per-file atomic replacement, and conflict-safe recovery/undo.
  • Updated VS Code integration, devcontainer snippets, and agent guidance.
  • Git metadata protection, absolute journal-path validation, and strict duplicate-field rejection across CLI and MCP.

Migration from 0.2

Bare writing commands now preview rather than execute. Update reviewed automation to use -y/--yes, or --write where a command has an interactive confirmation. No new --run flag was added.

gitpro plan
gitpro apply -y
gitpro pin -y /path/to/repository
gitpro setup --write

gitpro run --request FILE is a preflight until given -y, its reviewed plan token, and an idempotency key. Existing --fix, --rewrite, --generate, and --upload action flags retain their safeguards. --online alone does not grant write permission.

Setup and change approve --write still require terminal review. MCP writes remain disabled unless the operator enables them; clients cannot choose approval policies or approve themselves.

Regenerate managed devcontainer pin snippets after review with gitpro devcontainer --write -y; handwritten pin commands need an explicit execution flag. Keep custom generated identity files outside Git metadata directories.

A nonempty XDG_STATE_HOME must be absolute. For an older journal created with a relative path, select its existing absolute location before inspecting status or recovery; do not start replacement operations with new keys.

Install the attached artifacts

pipx install ./gitpro-0.3.0-py3-none-any.whl
code --install-extension ./gitpro-0.3.0.vsix

Verify the attached SHA256SUMS before installation. The VS Code extension requires a separately installed gitpro CLI.

Boundaries

Atomicity is per file, not a transaction across Git, the journal, configuration files, and GitHub. Unknown remote outcomes are not automatically retried. Host-enforced isolation is required for a real approval boundary against unrestricted same-UID processes; hooks are not sandboxed.

Linux, macOS, and VS Code CI covered the reviewed source. GitHub Enterprise was not separately exercised live.

Release qualification

Qualification completed using the exact wheel and VSIX attached to this release:

  • Wheel installed in a fresh virtual environment, with imports verified outside the source checkout.
  • VSIX installed in an isolated VS Code profile, activated in a real extension host, and resolved the expected identity through the installed CLI.
  • MCP refused writes by default, applied configuration only under an exact-path operator policy, and denied an out-of-scope output.
  • Live MCP commit, HTTPS push, and draft PR creation succeeded. Each exact-key replay returned the original outcome without repeating the write; read-only reconciliation observed the expected state without claiming causal attribution.
  • Merged-main CI, pilot push CI, and pilot PR CI passed all 15 jobs across Linux, macOS, and VS Code.
  • Temporary pilot PR #3 was closed without merging. Its branch was deleted using an exact-head lease.

The attached qualification.json records artifact hashes, source/pilot commits, CI links, and the pilot outcome. Private operation receipts and a consistent journal snapshot were retained separately. User Git identities and the active GitHub account were not changed by this release qualification.

Assets 7
Loading