Verify gets a lot smarter about what it checks and how it signals
Verify, Boss’s automated review step, now understands more kinds of code changes and reports its findings in a clearer way.
When a PR only moves files, deletes them, bumps dependencies, or changes generated code, Boss now recognizes these as routine housekeeping rather than behavior changes, and scopes its evidence checks accordingly. Proof video clips are now tied to specific claims, so each piece of evidence maps directly to the thing it is meant to prove.
When Verify parks a PR (decides it needs a human reviewer), it now posts a green status on GitHub and opens a review request, so reviewers get a normal GitHub notification and the PR does not look broken. While a PR is blocked or waiting, Verify posts a red status and keeps the PR as a draft, giving contributors a clear signal of where things stand.
Features
- Session timeline shows verify, build, and repair chats. You can now see the full sequence of automated activity for a session in one place, including which phase each chat belonged to.
- Session and chat lists show ticket IDs and short titles. Both the desktop and web views now display a ticket ID alongside a short title, making it easier to find the session you are looking for without memorizing long names.
- Verify findings can be filed as follow-up tickets. When Verify surfaces issues that are not blocking enough to stop a merge, an operator can now have them filed as tracked tickets automatically rather than letting them get lost.
- Verify-only sessions now exist as a distinct mode. Boss can run a verify pass on an externally created PR without treating it as something to build or auto-repair. Human-authored PRs can also be adopted into these sessions.
- Blockers from already-merged PRs are cleared automatically. If a build blocker was tied to a PR that has since merged, Boss now removes it without manual intervention.
- Review blockers that only touch unrelated files no longer stall builds. If a PR in review has no file overlap with the build candidate, Boss can proceed with selection rather than waiting indefinitely.
- Boss can now compute a confidence score for changes, based on blockers, affected areas, change size, and available proof.
- Defects can now be traced back to the PRs that introduced them. When a bug escapes into production, Boss can link it to the merged PRs that shipped it, making retrospectives more specific.
- Proof pages can be published through a configurable hook. Repositories can now provide their own publish hook to control where proof pages are uploaded, rather than relying on a hard-coded destination.
- Verify notes that were previously hidden are now visible. Advisory and review notes from both verify paths are now shown in a folded view, so nothing is silently dropped.
- An optional open-PR limit is available for automated builds. Teams that want to cap how many PRs are open at once can now configure a maximum, and the build cron will stop opening new PRs once that limit is reached.
Improvements
- Boss now labels PRs with their linked ticket automatically and keeps that tag up to date, even as heads move.
- When Boss is automatically rebasing a conflicted PR, it now labels the activity as “rebasing” so it is clear what is happening.
- Verify parks are now checked again after a PR sits parked, so conflicts that develop while waiting are caught and the rebase is started automatically.
- Retrospective notes from core-owned issues now route to upstream notes rather than being lost.
- Dependency overlap notes now include the names of the containing areas, making it easier to understand which parts of the codebase are affected.
- Stage gates now apply only to the configured team, rather than all teams in the tracker.
- Chat and session names in the automation are now shorter and include role labels, making it easier to read through activity logs.
Fixes
- Fixed an issue where sessions stuck in a “fixing checks” state with no active repair would stay stuck permanently and stop responding to PR events.
- Fixed an issue where draft PRs held by Boss could lose their ownership information across polling cycles, causing repair not to start.
- Fixed an issue where verify send-backs on draft PRs could become permanently unrepairable.
- Fixed an issue where a repair loop would repeat indefinitely when the underlying problem could not be fixed automatically. Boss now routes these cases to verify review instead.
- Fixed an issue where ticket verify holds were not surfaced as items needing attention, so they could be overlooked.
- Fixed an issue where duplicate verify sessions could both proceed, leading to conflicting verdicts.
- Fixed an issue where a PR session caught in a broken “fixing checks” state would silently drop every incoming PR event.
- Fixed an issue where stuck verify waits whose callbacks could never fire were not surfaced, leaving sessions in a silent hold.
- Fixed an issue where repair start contention could leave a block that was never retried or cleared.
- Fixed an issue where Boss could fail to start cleanly when PR association work ran at boot, occasionally causing a false connection error.