Repository navigation
chore: update tend workflows (0.2.11 → 0.2.13) - #880
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regenerates the nine
tend-*workflows against tend 0.2.13 (from 0.2.11). The committed diff is only the pinned action ref and theuvsetup version (0.12.13→0.12.17); everything below rides in the action and the plugin it loads.What changes for this repo
A cancelled gating check no longer reads as green.
poll_pr_checks.pynow treats onlySUCCESS,NEUTRAL, andSKIPPEDas green and exits 2 — unverified — on anything else (max-sixty/tend#1323). Cancelled runs are routine here: main serializes the complete suite, so a newer commit replaces the one waiting for its turn, andrunning-tendalready carries a rule for reading that shape. Under 0.2.11 a session polling its own push could report such a check as verified; it now has to say it could not verify.CI sessions ignore the bot's claude.ai account. Skills, plugins, and MCP connectors enabled on the
leaf-agentaccount no longer load into sessions that push and post as it (max-sixty/tend#1328). Sessions run with this repo's skills and tend's own, and nothing else./tmpis writable inside the sandbox, as scratch private to the run (max-sixty/tend#1324). A tool that hard-codes a/tmppath no longer needs an override;$TMPDIRstays the documented place to write.The sandbox launch retries a transient bridge-socket failure, up to three attempts (max-sixty/tend#1327). SRT gives socat 600 ms to bind, and a slow runner previously lost the whole job before the agent started.
Three plugin-side fixes also land:
review-runscan now cancel a run parked in GitHub'swaitingstate that holds its concurrency group without ever concluding (#1320);ground-claimsreads a past run's code at that run's commit rather than at the current default branch (#1319); andrun-tendcorrects its list of instruction paths restored to the base version on a PR (#1311).No configuration change needed
0.2.12 moved the agent into the job's own checkout through a copy-on-write view, which would have changed where dependency setup belongs. 0.2.13 reverts it (#1339):
setup:andsandbox_setup:behave as they did at 0.2.11, so.config/tend.yamlis unchanged here. This repo pins nomodel:, so the harness default applies as before.Full comparison: 0.2.11...0.2.13.