Repository navigation
v0.26.0 — Jenkins trigger and community fixes
A release of community fixes, a Jenkins trigger, and a round of dependency updates.
Highlights
- Jenkins trigger (#821). A Jenkins build can start any work: a Repo Task, a Job, a Local automation or a persistent agent's turn. Each
jenkinstrigger has its own URL and shared secret, takes the Notification plugin's JSON or a Jenkinsfilepoststep, and filters on result, job and branch. Seedocs/jenkins.md. The iOS and Android forms don't offer it yet. - Pick between GitLab servers (#802). With several GitLab servers set up, Add repository shows a button per server and lists the projects of the one you click.
Fixes
- Redis no longer fills up with finished repeat jobs (#814). Eight schedulers kept every finished tick, which ran small installs out of memory; they now keep the latest 10 completed and 50 failed, and an existing backlog is trimmed as the schedulers tick.
- PR reviews aren't cut off by idle cleanup (#824). A repo pod running a review is no longer removed mid-review.
- Agent sessions stay usable between turns (#826). A session between turns reads as ready instead of "Lost", and a repo session's turn uses the repo's coding turn limit (default 250) instead of the assistant's 20 steps.
- One
Defaultworkspace per new user (#801). Parallel first requests no longer create duplicates or fail with a 500. Duplicates that already exist are left as they are. - Readable marketplace skill sync errors (#805). A failed sync names the stage that failed and shows git's own message with a hint, and credentials in the source URL are redacted.
- The run-home sweep survives odd directory names (#825). A directory that isn't named after a run no longer aborts cleanup for that pod and the ones after it.
Dependencies and security
- Dependency updates across the API, web, CLI, the Android toolchain and the GitHub Actions the workflows use.
- The dependency audit accepts picomatch's GHSA-fc5q-39xc-vjpf while no patched release exists and picomatch stays in development tooling only. The gate fails again once a fix ships or picomatch reaches a production dependency.
Thanks to @ttbeast10, @MatanMeir, @matteslip, @NoelBank and @eyal4D for the contributions in this release.
Upgrade notes
No migrations; upgrading only takes a Helm upgrade:
helm upgrade optio oci://ghcr.io/jonwiggins/optio --version 0.26.0 -n optio --reuse-valuesFull changelog: https://github.com/jonwiggins/optio/blob/v0.26.0/CHANGELOG.md