docs(claude.md): document local-workflow update policy#265
Conversation
When `generator/pyproject.toml` exists (i.e. on the tend repo itself), Step 5 of the nightly skill now regenerates workflows via the in-tree generator instead of `uvx tend@latest`. Adopter repos without `generator/` fall through to the existing `uvx tend@latest` path unchanged. Motivation: PR #264 (from run 24330194038) ran `uvx tend@latest init` with PyPI's `tend` at 0.0.11 (released 2026-04-10). `main` has 10 generator commits landed since — #223 (drop hardcoded job timeouts), #225 (dedup review events), #227 (workflow_extra), #228 (paginate), #231 (inline-reply guidance), #233 (drop bot-author filter on issue_comment), #235 (prompt → skill), #254 (notifications freshness gate + bot-closed-PR drop), etc. Regenerating against the stale wheel reverted each of these. Maintainer flagged the PR as regressions; diagnosis confirmed the PyPI lag. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
I think instead we should just avoid upgrading the local workflows outside of releases |
Per maintainer feedback on #265: rather than running the in-tree generator during nightly, skip Step 5 entirely when generator/pyproject.toml exists. Workflow regeneration on tend itself happens as part of the release flow, not nightly — that avoids both PyPI-lag reverts and divergence between local workflows and the published generator. Adopter repos (no in-tree generator) continue to regen via uvx tend@latest.
tend-agent
changed the title
|
Agreed — that's the cleaner framing. Pushed 19aa2ae which replaces the in-tree-generator approach with an early skip in Step 5 when One note: with this change, the only path that updates tend's local workflows is the release flow, but the release skill doesn't currently include a regen step. Want me to open a follow-up PR adding |
|
let instead just make a note in our Claude.md that we update each night to the latest release; that it's ok to update earlier to the latest release; but not to update beyond it |
Replaces the nightly-skill skip with a CLAUDE.md note per maintainer guidance: workflows track the latest published release, can be updated to latest release at any time, but must not be pushed beyond it via the in-tree generator. The lag between a generator commit and the next release is expected. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
tend-agent
changed the title
|
Done — pushed 6b3d1dc which reverts the nightly-skill skip and adds a paragraph to CLAUDE.md documenting the policy: workflows track the latest published release, updating earlier to latest release is fine, in-tree generator should not push workflows beyond the latest release, and the lag between a generator commit and the next release is expected. PR title/description updated to match. |
3 participants
Summary
Per maintainer guidance (comment): document the local-workflow update policy in CLAUDE.md rather than adding skip logic to the nightly skill. Tend's
tend-*.yamlworkflows track the latest published release; nightly regen viauvx tend@latest initis the source of truth, updating earlier to the latest release is fine, and the in-tree generator should not push workflows beyond the latest release. The lag between a generator commit and the next release is expected and closes at the next release.The earlier nightly-skill skip is reverted; only CLAUDE.md changes remain.
Test plan
uvx tend@latest; reviewers reading CLAUDE.md understand the resulting "revert" PRs are expected during the post-commit/pre-release window