---
digest: >
  v0.30.2 gives Mirror's runtime git operations a timeout appropriate to
  what they actually do. Every git subprocess previously shared one
  2-second timeout, which is correct for local inspections but too short
  for network operations: during the v0.30.1 promotion, release-promote
  --push reported failure while the tag push had actually landed on the
  remote, forcing a manual recovery. Local commands keep the 2-second
  default; push and fetch call sites now use a 120-second network timeout,
  with a test asserting the network timeout stays meaningfully larger than
  the local one.
---

# v0.30.2 — Network-Appropriate Git Timeouts

**Date:** 2026-07-13

## Highlights

- `_run_git` no longer serves every git subprocess with a single
  2-second timeout.
- Local inspection call sites (`status`, `rev-parse`, `branch`, and
  similar) keep the 2-second default.
- Network call sites — `_git_push_ref`, `_git_fetch`, and the
  release-notes fetch path — now use a 120-second timeout.
- Six focused tests pin the behavior, including a guard that keeps the
  network timeout meaningfully larger than the local one.

## Where We Started

During the v0.30.1 promotion, `release-promote --push` reported failure
even though the tag push had actually landed on the remote. The runtime's
git helper served every subprocess call — local inspections and network
operations alike — with the same 2-second timeout. That budget is
reasonable for `git status` or `git rev-parse` on a local repository, but
it is not reasonable for `git push` or `git fetch` over the network, where
latency and remote-side processing can easily exceed a couple of seconds.
The mismatch turned a successful push into a false failure, forcing a
manual recovery step during an otherwise clean release.

## What Changed

`_run_git` call sites were split along one axis: local versus network.
Local inspection commands keep the existing 2-second timeout, since
correctness there depends on staying fast and responsive. Push (`_git_push_ref`)
and fetch (`_git_fetch`), along with the release-notes fetch path, now pass
an explicit 120-second network timeout. Six tests in
`tests/unit/memory/cli/test_runtime_git_timeout.py` pin this split,
including a guard test that fails if the network timeout is ever
tightened to be close to or smaller than the local timeout, preventing an
accidental regression back to the original bug.

## Conscious Exclusions

- No retry or backoff logic was added for network git operations — this
  release only corrects the timeout budget, not resilience against
  transient network failures.
- No change was made to how failures are reported downstream; a genuine
  timeout still surfaces as a failure, now simply after a budget that
  matches the operation's real network cost.

## Next Horizon

CV9 continues toward its done condition; this patch closes out the
release-promote reliability gap surfaced during the v0.30.1 promotion
without expanding scope beyond the timeout fix itself.
