docs: use pinned Foundry for semver-lock - #404
Open
Mabolla wants to merge 1 commit into
Open
Conversation
Collaborator
🟡 Heimdall Review Status
|
Mabolla
marked this pull request as ready for review
August 17, 2026 21:49
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
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.
Summary
foundryuprecovery step forsemver-lockfailures with the repository-pinnedmisetoolchainsemver-lockthroughmise execso local tooling matches the version pinned in.mise.tomlWhy
foundryupcan install a Foundry version that differs from the repository's pinned toolchain, which can leave contributors out of sync with CI and reproducibility-sensitive outputs such as semver-lock hashes and snapshots.Closes #403.
Validation
git diff --checkREADME.mdNote:
miseis not installed in the local Windows environment used for this documentation-only change, so the documented command itself was not executed locally.