chore: update tend workflows (0.2.14 → 0.2.15) - #122
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-*.yamlworkflows against tend 0.2.15 (from 0.2.14). The diff here is the action pin, onesetup-uvbump, and one step reordering intend-mention.yaml; the behavior changes ride in the action itself.What changes for this repo
tend-mention.yamlthe "Compute queue delay" step moved ahead ofactions/checkoutand thesetup:step. On this reposetup:does arustup component add llvm-toolsplus a nextest download, so the previously reported delay absorbed that install time; it now reports the wait for the job to start.AGENTS.override.mdis pinned to base on PR checkouts. It joinsCLAUDE.md,AGENTS.md, and the.claude/and.agents/trees in the instruction paths restored from the base commit, so a fork PR cannot introduce one that the session then reads as trusted instructions.tend checkbranch protection is stricter. It now requires a restrict-updates ruleset the bot cannot bypass, andtend check --fixcreates it. This repo already satisfies it —tend checkreportsPASS branch-protection:mainunder 0.2.15, and the one open failure (immutable-releases, tracked in tend check: configuration drift on max-sixty/cargo-affected #117) is unaffected.astral-sh/setup-uvv10.1.0 → v10.2.0 in thetend-mentionandtend-notificationspreflight jobs..config/tend.yamlis unchanged: it pins no model, and 0.2.15 does not change the harness model default.Upstream comparison: max-sixty/tend@0.2.14...0.2.15.
Upstream commits in this range
fix(review): say where GitHub shows a review's verdict, so the body opens with a finding(fix(review): say where GitHub shows a review's verdict, so the body opens with a finding tend#1362)fix(review): raise the bar for each further fix round on a PR with no human author(fix(review): raise the bar for each further fix round on a PR with no human author tend#1366)fix(review): focus a follow-up review on what was pushed, with the whole PR in view(fix(review): focus a follow-up review on what was pushed, with the whole PR in view tend#1368)fix(mention): compute the queue delay before checkout and setup(fix(mention): compute the queue delay before checkout and setup tend#1365)Require a restrict-updates ruleset, pin AGENTS.override.md, and rewrite the security docs(Require a restrict-updates ruleset, pin AGENTS.override.md, and rewrite the security docs tend#1367)chore: bump setup-uv to v10.2.0(chore: bump setup-uv to v10.2.0 tend#1359)Omitted as having no effect here: the 0.2.15 release commit and its workflow regeneration (max-sixty/tend#1358, max-sixty/tend#1369), tend's repo-local pin bumps (max-sixty/tend#1360), and the token-usage stream-json artifact copy (max-sixty/tend#1361), which was gated to tend's own repository.