pin lean-action fork with cache-key fix#174
Merged
Merged
Conversation
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.
The make-docs job's GitHub cache key didn't include the toolchain or manifest hash, because lean-action computes them from the repo root while our Lake package lives under
Lean/. That made the restore-key version-agnostic, so a stale.lakefrom an older Mathlib gets restored andlake exe cache getthen fails trying to check Mathlib out to the new revision — which is what broke make-docs on the v4.30 bump.This pins lean-action to a fork carrying the fix (leanprover/lean-action#167) until it's released upstream, at which point we switch back to the official action.