v0.5.0

Changelog

• ac586f1: assets: demo GIF, social preview, README hero (visual pass) (@Socialpranker)
• 9165e48: chore(release): GoReleaser + Homebrew tap + Dependabot (черновики) (@Socialpranker)
• 0ddc04d: chore(release): подготовка v0.5.0 — homebrew_casks + version bump (@Socialpranker)
• 6de1df5: docs(research): gap-audit — adoption, product, tech (ICE backlog) (@Socialpranker)
• c0efb0d: fix(rerun): пропускать uses:-шаги вместо смерти на первом же (@Socialpranker)
• 31be19a: fix(run): graceful Ctrl+C — отмена прогона вместо orphan-контейнеров (@Socialpranker)
• 91d9cad: fix(shell): реконструкция env + предупреждение о pull образа (#1) (@Socialpranker)
• 38bf6cd: fix(snapshot): не врать «snap ✓» когда docker commit упал (@Socialpranker)

v0.4.0 — lazygit-style TUI, command log, matrix picker

Three things, all borrowed shamelessly from what makes lazygit pleasant.

TUI (experimental). actdbg ui, or just actdbg in a terminal: jobs and steps on the left with live ▶ ✅ ❌ ⏭ statuses, the selected step's log streaming on the right, the last docker commands at the bottom. r runs the workflow, s drops you into the failed step's container, c/d show the fidelity and doctor reports, ? lists the keys. It is experimental in the honest sense: layout quirks are likely, and there is no screenshot yet because it has not earned one.

Command log. actdbg no longer hides what it does to your machine. Every docker command it executes is appended to ~/.actdbg/commands.log, mirrored in the TUI's bottom panel, and printed by actdbg run --show-commands.

Matrix picker. Jobs with strategy.matrix get a combination picker in the TUI before running; on the CLI the same filter is --matrix key=value (repeatable), with act's own selection semantics.

Internals: enginerun.RunWithTracker separates running from printing (the CLI and the TUI now share one code path), and the timeline tracker grew an OnLine callback for live log streaming.

Still true: a green local run does not guarantee green on GitHub — actdbg check explains where yours will differ.

actdbg 0.3.0 — replay a red run from its URL

CI is red? Paste the URL.

actdbg replay https://github.com/you/repo/actions/runs/123456

actdbg asks the GitHub API what failed (job, step, event, commit), checks your checkout matches the run's commit (--here to override), maps the job name back to the workflow (matrix-aware), and re-runs that job locally — then the debugger takes over: shell at the failed step, back N, rerun --from N.

This completes the loop the README promised: red run on GitHub → one command → your shell at the point of failure → fix → re-run from that step in seconds.

Honest limits: GitHub-side secrets and OIDC don't exist locally — steps needing them fail differently, and actdbg check lists exactly which ones before you chase a ghost. Private repos: set GITHUB_TOKEN.

go install github.com/Socialpranker/actdbg@latest

actdbg 0.2.0 — time-travel for CI

Time-travel arrived.

actdbg now docker commits the job container after every step. So:

• actdbg back 3 — a fresh container with the state exactly as it was right after step 3 (env included; --cmd for one-offs)
• actdbg rerun --from 5 — fix your workflow, re-run from the failed step in seconds, not minutes. The e2e in CI does the full cycle on real Docker: fail at step 2 → sed the fix → rerun --from 2 → step 3 runs → green.
• actdbg diff — step x-ray: files each step created/changed/deleted + its $GITHUB_ENV delta + timing

Honest limits, as always: rerun executes run: steps and stops at uses: actions with a message (full re-runs in v0.3); snapshots cost disk while you debug — actdbg clean wipes all of it; --no-snapshot opts out.

go install github.com/Socialpranker/actdbg@latest

actdbg 0.1.0 — stop at the failed step, get a shell

The missing debugger for GitHub Actions — first release.

• actdbg run — run a workflow locally, stop at the failed step, keep the job container alive, and drop into a shell with the step's environment (workflow env chain + everything earlier steps wrote to $GITHUB_ENV/$GITHUB_PATH).
• actdbg shell — re-enter that container any time later.
• actdbg check — fidelity report: the known ways a local run differs from GitHub, found statically in your workflow, with line numbers.
• actdbg doctor — your machine vs the classic act pitfalls (wrong image → command not found, arm64, docker group).
• actdbg clean — remove leftover act-* containers/networks.

Install: go install github.com/Socialpranker/actdbg@latest (Docker required).

Honest by design: a green local run is not a green GitHub run — actdbg tells you where they differ instead of pretending they don't. Built on nektos/act as a library (pinned v0.2.89). The e2e suite runs the real thing on GitHub's own runners: fail a step → verify the container survived and the env was reconstructed.

Next (v0.2–v0.3): time-travel snapshots (rerun --from N), per-step file/env diffs, replay <github-run-url>.