chore: update tend workflows (0.2.8 → 0.2.9) - #4164
Conversation
worktrunk-bot
left a comment
There was a problem hiding this comment.
The gh colour fix this bump carries (max-sixty/tend#1254) has a local sibling. .github/scripts/list-recent-runs.sh is this repo's own gh --json reader and still guards with export NO_COLOR=1 alone — the guard that fix found insufficient, since gh ranks a forced CLICOLOR_FORCE above NO_COLOR. Its gh run list --json … output feeds straight into jq -s 'add', so escape codes there fail the parse rather than degrade it.
The script is also unreferenced: git grep list-recent-runs matches nothing outside the file itself, because #1676 deleted its only consumer (claude-hourly-review-reviewers.yaml) when review-reviewers moved to the tend repo. Deleting it settles both points.
Worth doing on its own branch rather than folding in here: this PR's verifiability rests on uvx tend@0.2.9 init reproducing it byte-for-byte, and an unrelated deletion costs that.
Regenerates the
tend-*.yamlworkflows with tend 0.2.9 (from 0.2.8) and moves themax-sixty/tend/claudeaction pin with them.Two changes reach the generated files:
ghJSON reads are no longer corrupted by a forced-colour environment. Thepreflight scripts in
tend-mentionandtend-notificationsparsegh --jsonoutput; when the job environment forces colour,
ghwrites ANSI codes into thatpiped response and the parse sees them. Both readers now run
ghwithNO_COLOR=1andCLICOLOR_FORCE=0—ghranks a forced value aboveNO_COLOR,so the second variable is the one that actually settles it
(fix: defeat a forced-colour environment in every gh reader tend#1254).
tend-mention-relayrecords why it carries no pause check. Comment only: therelay job boots no agent, and
TEND_ENABLED=falsealready skips the jobs that do,so a paused repo relays an event that then reaches nothing
(docs(mention-relay): record why the relay carries no TEND_ENABLED check tend#1258).
The action bump also picks up the bundled-skill changes at that ref, which change
how the bot behaves rather than what the workflow files say: it now reviews a change
before the push that opens or fixes a PR (max-sixty/tend#1259), and the
running-in-cireferences index is keyed by when to read each file(max-sixty/tend#1253).
Release mechanics and tend-internal test/doc fixes in the range are omitted.
Full comparison: max-sixty/tend@0.2.8...0.2.9
.config/tend.yamlpins no model, so nothing there needed updating.