chore(seidroid): bump driver floor to v0.18.0 via uci - #546
Conversation
Points at sei-protocol/uci's seidroid-review.yml at the commit that raises the driver floor to v0.18.0 (sei-protocol/sei-internal-skills), carrying two transport fixes traced to a recurring no-verdict crash rate on this workflow: mint the machine-credential token on the health-checked transport (uci#420-equivalent upstream fix), and retry a session lookup that never reached the server instead of failing the run outright. See sei-protocol/uci#106 for the full change this SHA carries. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
PR SummaryLow Risk Overview That upstream pin raises the reviewer driver floor to v0.18.0, which is intended to cut intermittent review failures (transport/token minting on a health-checked client and retry when a session lookup never reached the server). This repo depends on that commit existing in Reviewed by Cursor Bugbot for commit 73b2a7c. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
This review did not complete. It reached no verdict, so there is no review of this change to act on. This review produced no decision that could be read mechanically. the run deadline expired before the turn replied The agent's own reply is not published: a reply this driver cannot attribute to its own turn is one it must not repeat here. This run's log names the session that produced it. Read this run for the rest: https://github.com/sei-protocol/sei-k8s-controller/actions/runs/34539362070 |
Bumps this repo's three
seidroid-review.ymlreferences fromsei-protocol/uci@d895e04to@92f74c9-- the commit that raises the reusable workflow's driver floor fromv0.17.0tov0.18.0.v0.18.0 (sei-internal-skills) ships two transport fixes traced to a recurring ~20-29% no-verdict crash rate on seidroid-review across all five repos that use this workflow: mint the machine-credential token on the health-checked transport instead of a bare client with no dead-connection detection, and retry a session lookup that never reached the server instead of failing the run outright.
Depends on sei-protocol/uci#106 landing first (or at minimum, this SHA staying reachable in that repo -- it doesn't require the uci PR to merge into
uci'smain, only that the commit exists).Not merging this myself -- opening for review.
🤖 Generated with Claude Code