Repository navigation
chore: update tend workflows (0.2.11 → 0.2.13) - #4215
Merged
Merged
Conversation
This was referenced Sep 21, 2026
max-sixty
pushed a commit
that referenced
this pull request
Sep 21, 2026
…#4217) `main` now pins `max-sixty/tend/claude@0.2.13` (#4215, merged as `c5e17139a`), and two sandbox facts this overlay asserts stopped being true of the sandbox sessions actually run in. **Root `/tmp` is writable.** [max-sixty/tend#1324](max-sixty/tend#1324) ("Make /tmp writable inside the sandbox") merged 2026-09-19, after 0.2.11 and before 0.2.12. In the `0.2.11...0.2.13` diff the sandbox's own SRT test flips its probe: `touch /tmp/tend-unscoped` must fail at 0.2.11, while at 0.2.13 `touch /tmp/tend-sandbox-scratch` must succeed and `/var/tmp` is the refused one. Tend dropped the matching paragraph from its bundled `run-tend` skill in the same range, along with the `TMPPREFIX` override whose comment said it existed only because zsh's here-document default "sits in the read-only root /tmp". **The agent workspace container moved to `/var/tmp`.** `prepare_agent_workspace.py` at 0.2.13 calls `mkdtemp(prefix="tend-agent-workspace-", dir="/var/tmp")`, so the slugified session-log directory is `-var-tmp-…`, not `-tmp-…`. Neither edit changes what a session should do. `${TMPDIR:-/tmp}` is still where scratch files belong, and the log-path section's conclusion — there is no literal to match on, so use `find "$DEST" -name '*.jsonl'` — is if anything better supported by a container that moves between releases. What goes is the justification attached to each, which is the part that could go stale and did. The old text was accurate right up to the merge: a write probe in this run, still on 0.2.11, is refused with `Read-only file system`. It is wrong from the next session on, which is why this is a deletion rather than a rewrite — the overlay is better off not restating a boundary tend owns and moves. <details><summary>Where this was found</summary> The `tend-review` session on #4215 ([run 35570800500](https://github.com/max-sixty/worktrunk/actions/runs/35570800500)) noticed the overlay would go stale on merge and deliberately left it alone, on the grounds that `.claude/**` is restored from the base branch during a review session and a separate PR is the cleaner home. This is that PR, opened from the `tend-review-runs` sweep that can edit `.claude/skills/` from a `$TMPDIR` worktree. </details> Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
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
2 participants
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
tend-*workflows with tend 0.2.13 (from 0.2.11). Mechanically the diff is the action pinmax-sixty/tend/claude@0.2.11→@0.2.13in the eight workflows that run the agent, theastral-sh/setup-uvpin0.12.13→0.12.17in the two that install uv directly (tend-mention,tend-notifications), and a regenerated header comment in all nine.The upgrade that matters for this repo is in CI polling.
poll_pr_checks.pypreviously treated any gating check that settled without a red conclusion as green — so a required check belonging to a cancelled or stale run, or aCOMPLETEDcheck carrying no conclusion at all, let the bot report a PR as green when nothing had actually verified it. 0.2.13 splits those out asunverifiedand givespolla distinct exit code for them (max-sixty/tend#1323). Practically: fewer "checks went green" claims on PRs whose required jobs were cancelled, at the cost of some polls ending unverified rather than green.The rest, in rough order of how visible it is here:
tend-outageissue, so it should show up as fewer of those./tmpis writable inside the sandbox (Make /tmp writable inside the sandbox tend#1324); therun-tendskill's note that it was read-only is gone. This repo'srunning-tendskill still restates that note, so it goes stale when this merges — I'll follow up separately rather than mix a skill edit into the generated-workflow diff.run-tendskill's description of which paths get restored from the PR base, and on which events, was wrong in 0.2.11;.agents/is now named alongside.claude/, and the event list is corrected (fix(skills): correct run-tend's list of restored instruction paths and events tend#1311). The restore behavior itself is unchanged..config/tend.yamlpins no model, so the harness-default check found nothing to adjust.Full comparison: max-sixty/tend@0.2.11...0.2.13
Copy-on-write sandbox view: landed and reverted within this range
max-sixty/tend#1333 and max-sixty/tend#1334 moved the agent into the job's own checkout and home through a copy-on-write view; max-sixty/tend#1339 reverted both before 0.2.13. Nothing from that work is in this diff — noted so a later reader doesn't chase it out of the commit list.