Skip to content

fix: CD and toolchain workflow fixes from the cell template - #20

Merged
fgdorais merged 3 commits into
mainfrom
claude/cell-workflows
Nov 9, 2026
Merged

fgdorais merged 3 commits into
mainfrom
claude/cell-workflows

Conversation

@fgdorais

@fgdorais fgdorais commented Nov 6, 2026 •

Copy link
Copy Markdown
Owner

This brings over the CD/toolchain workflow fixes from the Batteries cell template. When main is merged into nightly-testing, nightly-testing now takes main's lakefile.toml and keeps only its own rev for each [[require]] (and its own toolchain and manifest), running lake update on the nightly toolchain if the lakefile changed. The main toolchain update now always uses one update-main-toolchain branch, so a new release candidate updates the open PR instead of opening another one. Where the CD concurrency group was keyed on github.head_ref (empty on push), it is now keyed on github.ref.

Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

The CD pipeline merged lakefile.toml textually with -X ours, which drops
main's changes whenever they touch lines next to nightly-testing's
dependency revisions. Now take main's lakefile.toml and only carry over nightly-testing's
dependency revisions. When the lakefile changes, refresh the manifest with
`lake update` on the nightly toolchain.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`github.head_ref` is empty on push events, so every CD run shared the
group `cd-`. Use `github.ref` so main and nightly-testing runs no longer
queue behind (or cancel pending runs of) each other.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The PR branch was named after the toolchain version, so each new release
candidate opened a new PR and left the previous one open. Use a fixed
branch so the existing PR is updated in place instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fgdorais
fgdorais merged commit f7e876e into main Nov 9, 2026
1 check passed
@fgdorais
fgdorais deleted the claude/cell-workflows branch November 9, 2026 17:00
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