chore: update tend workflows (0.2.5 → 0.2.6) - #6308
Conversation
prql-bot
left a comment
There was a problem hiding this comment.
This branch carries #6307's commit (553cd4f5289f67461d6021001f1aa8f332e5b023) — the three grammars/prql-lezer/ files in this diff are that PR's entire content, not a regeneration artifact. Merging #6308 as it stands merges the lezer grammar change under a chore: update tend workflows title that doesn't mention it, and puts that change through review twice: once here and once on #6307.
The third paragraph of the PR body says the opposite — that the nightly base fix "is what keeps this PR standing alone on main". It doesn't, because the fix ships in 0.2.6 and the regeneration session ran under 0.2.5; it takes effect from the next nightly regen onwards. Rebasing drops the commit and makes the claim true of the diff:
git rebase --onto origin/main 553cd4f5289f67461d6021001f1aa8f332e5b023 tend/update-workflowsThat leaves the eight workflow files, and #6307's own review covers the grammar change where it belongs. The body's third paragraph needs rewording to match at the same time.
The regenerated workflows themselves look right: the mention_verify.py change returns "no dispatch" for a bot-authored review only after the body and inline @prql-bot mention checks have run, so a human naming the bot in a review still summons a session, and the human-PR path reaches the same verdict it did before. The read-only /tmp that 0.2.6 fixes is live right now — this review session's review_preflight.py start aborted with OSError: [Errno 30] Read-only file system: '/tmp/reviewed-head' and needed its paths redirected by hand, so every tend session on main is paying that until this merges.
2d9d886 to
3323708
Compare
|
Rebased onto The third paragraph of the body is reworded to match: the base fix ships in 0.2.6, so it applies from the next nightly regeneration onwards rather than to this one — the stacking here was undone by hand. |
Regenerates the eight
tend-*workflows with tend 0.2.6, up from 0.2.5.Two of the three changes land in this diff as behavior; the third takes effect through the pinned action.
A review the bot writes on its own PR no longer costs a second session. Until now,
tend-mention.yamldispatched an author session whenevertend-reviewreviewed a bot-authored PR, and that session applied the findings. The review run now does both itself — submits the review, pushes the fixes as one batch, and polls CI — the same shape it already used on Dependabot and renovate PRs.mention_verify.pycorrespondingly returns "no dispatch" for a review the bot wrote, which is the bulk of thetend-mention.yamlchange here. Reviews on human-authored PRs are unaffected, and a human naming the bot in a review still summons a session. (max-sixty/tend#1203)Nightly's regeneration branch is now based on the fetched default branch rather than the checkout's
HEAD. A sweep that opens a survey PR before reaching the regeneration step stacks this PR on that branch, putting the same workflow diff through review once per link. The regeneration session that opened this PR ran under 0.2.5 and hit exactly that ordering — #6307 was opened first, and its commit came along — so the branch was rebased ontomainby hand and now carries the eight workflow files alone. The fix ships in 0.2.6, so it applies from the next nightly regeneration onwards. (max-sixty/tend#1201)Sandboxed agents get a writable
TMPDIRunder the sandbox home, with root/tmpleft read-only. Bundled scripts and skill recipes write there instead of hardcoding/tmp. Under 0.2.5 the read-only/tmpis already in force while the scripts still write to it, so the nightly regeneration script aborted onOSError: [Errno 30] Read-only file systemand needed its paths redirected by hand; 0.2.6 removes that. (max-sixty/tend#1199)No model pins to review —
.config/tend.yamlsets none, and the release changes no harness model default.Full comparison: 0.2.5...0.2.6.