Skip to content

docs: use pinned Foundry for semver-lock - #404

Open
Mabolla wants to merge 1 commit into
base:mainfrom
Mabolla:agent/fix-pinned-foundry-docs
Open

docs: use pinned Foundry for semver-lock#404
Mabolla wants to merge 1 commit into
base:mainfrom
Mabolla:agent/fix-pinned-foundry-docs

Conversation

@Mabolla

@Mabolla Mabolla commented Aug 17, 2026

Copy link
Copy Markdown

Summary

  • replace the foundryup recovery step for semver-lock failures with the repository-pinned mise toolchain
  • run semver-lock through mise exec so local tooling matches the version pinned in .mise.toml

Why

foundryup can 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 --check
  • verified the change is limited to README.md

Note: mise is not installed in the local Windows environment used for this documentation-only change, so the documented command itself was not executed locally.

@cb-heimdall

Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/2
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 1
Sum 2

@Mabolla
Mabolla marked this pull request as ready for review August 17, 2026 21:49
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.

docs: foundryup recommendation can install a version different from the repository-pinned Foundry toolchain

2 participants