February 15, 20260.1.26Jugg.ai
v0.1.26 — fix: handle GitHub permission errors in testing agent CI dispatch
Release v0.1.26: Fix GitHub Permission Error Handling in Testing Agent
February 15, 2026
What changed
- Fixed a pipeline crash when the GitHub App installation lacked
actions:writepermission. The testing agent's CI dispatch step now catches"Resource not accessible by integration"errors instead of failing the entire pipeline. - New helper:
isWorkflowDispatchPermissionError()— consolidates 5 known GitHub API permission error patterns (including the newResource not accessible by integration, lowercase variant, and fine-grained PAT errors) into a single reusable check. - Graceful skip behavior — permission errors are now treated the same as a missing workflow file: CI is skipped and the pipeline continues to the release stage.
- 19 new tests covering all permission error patterns and CI fix detection logic.
Why it matters
Pipeline runs no longer fail silently when GitHub App permissions aren't fully configured. Instead of crashing, the testing agent skips CI and lets the pipeline proceed — making the system more resilient to permission misconfigurations.
Technical notes
detectCIFixandisWorkflowDispatchPermissionErrorare now exported fromsrc/inngest/agents/testing.ts- No database or schema changes
- No breaking changes
Release Notes
Successfully merged PR #77 and published release v0.1.26.
PR #77: fix: handle GitHub permission errors in testing agent CI dispatch
- Squash merged to main (SHA: 74ad208de715dca9c729033b1e50ba7855d62270)
Release v0.1.26: https://github.com/Jugg-ai/Jugg-ai.jugg-ai/releases/tag/v0.1.26
Summary of changes:
- Fixed a bug where the testing agent crashed when the GitHub App lacked
actions:writepermission - Added
isWorkflowDispatchPermissionError()helper covering 5 known permission error patterns - CI dispatch now gracefully skips instead of crashing the pipeline on permission errors
- Added 19 new test cases for the permission error detection and CI fix detection logic