[marcusrbrown]

The Semantic Release step takes about 10 minutes. About 8 of those are spent running our pre-push hook twice.

.github/actions/setup runs bun install, and its postinstall (simple-git-hooks) installs the repo's git hooks on the release runner. semantic-release then pushes twice, once for the release commit and once for the tag. Each push fires pre-push, which runs bun install, lint, build and a dist diff. CI and the Build release step have already done all of that.

Run 41037504998 (v0.130.0) shows the cost:

Phase	Time
@semantic-release/git prepare (commit + push)	2.5 min
Tag push	5.3 min
Release-notes narration watch	2.4 min

This sets SKIP_INSTALL_SIMPLE_GIT_HOOKS: '1' on the Perform Release job. With it set, simple-git-hooks skips installing the hooks, so neither push runs them. The narration watch is intentional and stays as it is.

The next release's Semantic Release step should take about 2.5 minutes.

[fro-bot]

Verdict: PASS

The job-scoped flag reaches the composite setup action's bun install. The installed simple-git-hooks implementation recognizes '1' and exits before installing hooks, achieving the intended release optimization.

Blocking issues

None

Non-blocking concerns

None

Missing tests

None. No additional automated tests are warranted for this narrowly scoped configuration change. Review was static; no tests or build, lint, or type-check commands were run.

Risk assessment (LOW): likelihood of regression, security exposure, or blast radius

Limited to hook installation in the release job on a fresh hosted runner. The explicit release build remains in place; no permissions or public APIs change. Actual timing improvement remains to be confirmed by the next release.

---

Run Summary

Field	Value
Event	pull_request
Repository	fro-bot/agent
Run ID	41046558461
Cache	hit
Session	ses_e73794d9dffeE3OZbUqtXGRyhI