Skip to content

v1.4.5 · Isolated checks and resumable validation

Choose a tag to compare

@jonathankems jonathankems released this 11 Oct 21:00
0a94b03

Fixed

  • execute workers can run focused checks and prerequisite builds in parallel when their resources are isolated. Required full suites and final builds run on the combined change, unless repository policy requires them earlier.
  • code-cleanup prefers supported resource isolation or shared locks. Resource acquisition defaults to a five-minute timeout. Deferred checks retain their check record and resume once their resume condition is met. Test execution keeps its own timeout.
  • code-review reports deferred checks as unverified with their resume condition. execute, clean-up, submit, and deploy preserve those records and resume the checks once the resume condition is met. submit and deploy stop before delivery and continue from their preparation step when run again. Required deferred checks prevent delivery until verified.
  • setup-snappedly-skills records shared resources, isolation or locking commands, and configured resource-acquisition timeouts. Unknown resource scope stays unverified.

Updating existing repositories

Rerun setup-snappedly-skills to refresh Concurrent runs in docs/agents/workflow.md. Setup preserves team requirements and corrects entries that classify worktree-local output as shared.