Repository navigation
chore: update tend workflows (0.2.11 → 0.2.13) - #118
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 with tend 0.2.13, up from 0.2.11. The diff is the action pin on every workflow plus theuvversiontend-mentionandtend-notificationsinstall (0.12.13 → 0.12.17); no job, trigger, permission, or concurrency change.What the upgrade changes for this repo:
poll_pr_checks.pyderived "green" by subtraction, so a check that completed without a usable conclusion — the shape a concurrency cancellation produces when a second push supersedes the first — landed in neither the pending nor the failed bucket and the poll exited 0. Green is now an allowlist (SUCCESS,NEUTRAL,SKIPPED), andCANCELLED,STALE, or any conclusion GitHub adds later exits 2, whichmonitor-cialready reads as unverified (fix(poll): report a cancelled gating check as unverified, not green tend#1323). The reviewer-facing half moved with it: the approval path now names such a check as unverified beside the verdict instead of assuming a replacement run covered it, so an approval no longer reports the commit green when nothing actually passed. That matters here because every bot PR on this repo is polled against a pinned commit./tmpis writable inside the sandbox. It was read-only, so a scratch path a session composed by hand under/tmpfailed withRead-only file systemwhile$TMPDIRand the checkout worked. The runner-owned containers moved to/var/tmpand stay unwritable from inside (Make /tmp writable inside the sandbox tend#1324).syncClaudeAiSkills: false,syncClaudeAiPlugins: false, anddisableClaudeAiConnectors: true, keeping the instruction and tool sources to the composite action and the tend marketplace (fix(claude): keep the bot's claude.ai account out of CI sessions tend#1328).run-tendnow names.agents/among the instruction paths restored from the base branch on a PR, and states the restore as a condition on the checkout rather than an event list that had gone stale for relayed review events — both errors told a session a path was unpinned when it was pinned, which is the direction that loses a contributor's edit (fix(skills): correct run-tend's list of restored instruction paths and events tend#1311).ground-claimsnow says to read a past run's code at that run'shead_sharather than at the current default branch (skills(ground-claims): read a past run's code at that run's commit tend#1319).review-runsgained the case where a run parked inwaitingholds a concurrency group forever and the workflow silently stops running (skills(review-runs): find a workflow wedged behind a run parked inwaitingtend#1320).post-to-githubgained the matching carve-out to the#L-link rule for a body that explains a past run (skills(ground-claims): read a past run's code at that run's commit tend#1319).claudeCLI pin moves 2.1.270 → 2.1.278. A default on the composite action rather than anything in these workflows, so it is invisible in this diff, but it is the agent runtime every tend session here runs on (chore: bump claude-code to 2.1.278 tend#1330).Upstream comparison: max-sixty/tend@0.2.11...0.2.13
The copy-on-write sandbox view shipped in 0.2.12 and was reverted before 0.2.13 after it broke
git add -Ain the agent's checkout, so it is not part of this upgrade (max-sixty/tend#1339).