Pin lean-toolchain to leanprover/lean4:v4.29.0#11
Open
astefano wants to merge 1 commit into
Open
Conversation
`lean-toolchain` contained `master`, which elan cannot resolve (`error: no such release: 'master'`), breaking CI and clean checkouts. Pin to `leanprover/lean4:v4.29.0` — a concrete, elan-resolvable release that loom2's current source builds on. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
astefano
force-pushed
the
fix/lean-toolchain-nightly
branch
from
June 4, 2026 11:42
89c0733 to
a92c59c
Compare
astefano
changed the title
lean-toolchain to an elan-resolvable channellean-toolchain to leanprover/lean4:v4.29.0
astefano
marked this pull request as ready for review
June 4, 2026 11:46
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
1 participant
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.
lean-toolchaincontainedmaster, which elan cannot resolve (error: no such release: 'master'), so CI fails at the Elan install step and clean checkouts fail too.This pins it to
leanprover/lean4:v4.29.0, a concrete elan-resolvable release. I first triedleanprover/lean4:nightly(resolves fine), but the current source does not compile onnightly-2026-06-04(type error inLoom/WP/Basic.lean:398), so I pinnedv4.29.0instead.Verified end-to-end on my fork (with the workflow placement from #9 and the
-j1lakefile fix applied): full green build — all 22 jobs, includingLoom,Main, and theloom2exe.Note: green CI requires #9 (workflow location) and the
lakefile.tomlthread-stack fix as well; this PR is just the toolchain pin. If you prefer to stay on the dev channel, a pinnedleanprover/lean4:nightly-YYYY-MM-DDthat your source builds on would also work.Closes #10.