Skip to content

chore: update tend workflows (0.1.24 → 0.2.0) - #382

Merged
max-sixty merged 1 commit into
mainfrom
tend/update-workflows
Sep 7, 2026
Merged

max-sixty merged 1 commit into
mainfrom
tend/update-workflows

Conversation

@leaf-agent

@leaf-agent leaf-agent commented Sep 7, 2026 •

Copy link
Copy Markdown
Collaborator

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

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

@max-sixty
max-sixty merged commit 6264762 into main Sep 7, 2026
4 checks passed
@max-sixty
max-sixty deleted the tend/update-workflows branch September 7, 2026 16:04
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>
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.

2 participants