Repository navigation
chore: update tend workflows (0.1.24 → 0.2.0) - #382
Merged
Merged
Conversation
max-sixty
pushed a commit
that referenced
this pull request
Sep 7, 2026
Tonight's nightly regeneration of the tend workflow files, which moves this repo from tend 0.1.24 to 0.2.0. **tend version:** 0.1.24 → 0.2.0 **Notable changes** - Every job now opens with a `Check whether tend is enabled` step that reads `.config/tend.yaml` from the default branch and gates the rest of the job on it (max-sixty/tend#1132). This is a runtime kill switch: setting `enabled: false` on `main` stops every tend job without regenerating a workflow. It accounts for most of the added lines here, since the check is inlined once per job. This repo's config sets no `enabled` key, so the default `true` applies and behaviour is unchanged. - The runner logic moved out of inline Bash and skill prose into tend's own Python (max-sixty/tend#1158), which is why `tend-mention`'s `verify` and `tend-notifications`' pre-check bodies are rewritten even though what they decide is unchanged. - Workflows gained Claude effort/harness arguments (max-sixty/tend#1161) and experimental Codex subscription auth (max-sixty/tend#1159), so the harness a job runs under is configurable per repo. Neither is set here. - `ci-fix` now takes a concurrency group per branch and watched workflow (max-sixty/tend#1148), so two failing workflows on the same branch no longer cancel each other's fix run. That matters here, where `ci-fix` watches both `ci` and `publish-site`. - Review behaviour: a standing bot approval is dismissed when a later review withholds the verdict (max-sixty/tend#1136) or when another PR merging invalidates it (max-sixty/tend#1139). - `tend check` paginates its secret listings (max-sixty/tend#1137), so a repo with more than one page of secrets can no longer pass the allowlist check by omission. **Verification** Regenerating with `uvx tend@0.2.0 init` against this repo's `.config/tend.yaml` reproduces all eight workflow files byte for byte, so nothing here is a hand-edit and every repo customization (the `setup:` uv steps, `bot_name`, the `ci-fix` watched workflows) survived. `.github/actionlint.yaml` is unchanged by 0.2.0. Full comparison: max-sixty/tend@0.1.24...0.2.0 Co-authored-by: leaf-agent <318509791+leaf-agent@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
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.
Tonight's nightly regeneration of the tend workflow files, which moves this repo from tend 0.1.24 to 0.2.0.
tend version: 0.1.24 → 0.2.0
Notable changes
Check whether tend is enabledstep that reads.config/tend.yamlfrom the default branch and gates the rest of the job on it (Add runtime switch for Tend workflows tend#1132). This is a runtime kill switch: settingenabled: falseonmainstops every tend job without regenerating a workflow. It accounts for most of the added lines here, since the check is inlined once per job. This repo's config sets noenabledkey, so the defaulttrueapplies and behaviour is unchanged.tend-mention'sverifyandtend-notifications' pre-check bodies are rewritten even though what they decide is unchanged.ci-fixnow takes a concurrency group per branch and watched workflow (Give ci-fix a concurrency group per branch and watched workflow tend#1148), so two failing workflows on the same branch no longer cancel each other's fix run. That matters here, whereci-fixwatches bothciandpublish-site.tend checkpaginates its secret listings (fix(checks): paginate the secret listings, so page 2 can't pass as clean tend#1137), so a repo with more than one page of secrets can no longer pass the allowlist check by omission.Verification
Regenerating with
uvx tend@0.2.0 initagainst this repo's.config/tend.yamlreproduces all eight workflow files byte for byte, so nothing here is a hand-edit and every repo customization (thesetup:uv steps,bot_name, theci-fixwatched workflows) survived..github/actionlint.yamlis unchanged by 0.2.0.Full comparison: max-sixty/tend@0.1.24...0.2.0