gh-aw v0.90.1 (2026-09-30T17:20:00Z) adds standalone safe-output-backed ledgers with replay projections (defaults preserved on shared-workflow import), richer audit/usage artifacts (ledger txs, threat-detection outcomes, experiment/evals, friction costs), narrowed add-labels + required-labels gating for assign-to-agent, compile-time self-hosted runner enforcement, kebab-case sandbox frontmatter, and Claude Code CLI pin 2.1.280.
Key Takeaways
- ✓v0.90.1 at 2026-09-30T17:20:00Z after v0.90.0
- ✓Standalone safe-output ledgers + replay; defaults kept on shared-workflow import
- ✓Richer audit: ledger txs, threat detection, evals, friction-cost attribution
- ✓Governance: narrowed add-labels; required-labels on assign-to-agent; compile-time self-hosted runner enforcement
- ✓Claude Code CLI pin 2.1.280; docs via gh-aw README / GitHub Next project page
Key Decision Metrics at a Glance
Not enough VRAM? Compare cloud API and self-hosting costs
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Background
Agentic workflows that mutate issues/PRs need replayable ledgers and threat-detection artifacts. After v0.90.0’s friction-cost/noop graders, 0.90.1 hardens ledger independence and self-hosted runner policy.
What shipped
Standalone safe-output ledgers + replay (defaults kept on import); richer audit (txs, threat outcomes, evals, friction attribution); narrowed add-labels + required-labels on assign-to-agent; compile-time self-hosted runner enforcement; kebab-case sandbox frontmatter; Claude Code CLI 2.1.280.
Benchmarks
No SWE-bench. Anchor: 2026-09-30T17:20:00Z; compare v0.90.0...v0.90.1. Release note mentions ~13.3 AIC workflow self-metrics—not a cross-product bench.
Get started
Upgrade to v0.90.1; see https://github.com/github/gh-aw/blob/main/README.md and https://githubnext.com/projects/agentic-workflows
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.