Skip to content

chore: update tend workflows (0.2.9 → 0.2.10) - #6330

Merged
max-sixty merged 1 commit into
mainfrom
tend-0.2.10
Sep 17, 2026
Merged

max-sixty merged 1 commit into
mainfrom
tend-0.2.10

Conversation

@max-sixty

Copy link
Copy Markdown
Member

Regenerates the tend workflows from tend 0.2.10 (was 0.2.9).

0.2.10 restores sandbox launch. bubblewrap's CVE-2026-87766 fix
(0.9.0-1ubuntu0.2 on noble) opens each component of a bind destination
with O_DIRECTORY where it used to stat it, so an intermediate directory
now needs read permission and not just search. Tend left the agent
workspace container traverse-only, so from the afternoon of 2026-09-17,
when the Ubuntu archive began serving the update, every session died
before the agent turn started:

bwrap: Can't mkdir parents for /tmp/tend-agent-workspace-*/checkout: Permission denied

0.2.10 opens that container to 0o755; the checkout inside it stays
0o700 until the handoff (#1277).

That fix does not appear in this diff — it lives inside the composite
action, which these workflows pin to an immutable release tag, so
regenerating onto 0.2.10 is what carries it here. The one visible change
beyond the pin is in the tend-notifications preflight: its bot-PR
conflict scan now counts only a settled CONFLICTING. GitHub computes
mergeable lazily, so the first read after the base branch moves returns
UNKNOWN, which was booting a session after every merge into the default
branch (#1276).

The pin carries the rest of 0.2.10 too — bundled skill changes, and the
sandbox seeding the agent's Git commit identity before the turn starts,
among others.

Release notes: https://github.com/max-sixty/tend/releases/tag/0.2.10

This was written by Claude Code on behalf of max-sixty

🤖 Generated with Claude Code

Regenerates the tend workflows from tend 0.2.10 (was 0.2.9).

0.2.10 restores sandbox launch. bubblewrap's CVE-2026-87766 fix
(`0.9.0-1ubuntu0.2` on noble) opens each component of a bind destination
with `O_DIRECTORY` where it used to stat it, so an intermediate directory
now needs read permission and not just search. Tend left the agent
workspace container traverse-only, so from the afternoon of 2026-09-17,
when the Ubuntu archive began serving the update, every session died
before the agent turn started:

    bwrap: Can't mkdir parents for /tmp/tend-agent-workspace-*/checkout: Permission denied

0.2.10 opens that container to `0o755`; the checkout inside it stays
`0o700` until the handoff (max-sixty/tend#1277).

That fix does not appear in this diff — it lives inside the composite
action, which these workflows pin to an immutable release tag, so
regenerating onto 0.2.10 is what carries it here. The one visible change
beyond the pin is in the `tend-notifications` preflight: its bot-PR
conflict scan now counts only a settled `CONFLICTING`. GitHub computes
`mergeable` lazily, so the first read after the base branch moves returns
`UNKNOWN`, which was booting a session after every merge into the default
branch (max-sixty/tend#1276).

The pin carries the rest of 0.2.10 too — bundled skill changes, and the
sandbox seeding the agent's Git commit identity before the turn starts,
among others.

Release notes: https://github.com/max-sixty/tend/releases/tag/0.2.10

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@max-sixty
max-sixty merged commit 7ba6c90 into main Sep 17, 2026
39 of 40 checks passed
@max-sixty
max-sixty deleted the tend-0.2.10 branch September 17, 2026 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant