Skip to content

ci: pin Foundry to v1.3.6 for reproducible formatting#91

Open
amiecorso wants to merge 1 commit into
mainfrom
ci/pin-foundry-fmt-v1.3.6
Open

ci: pin Foundry to v1.3.6 for reproducible formatting#91
amiecorso wants to merge 1 commit into
mainfrom
ci/pin-foundry-fmt-v1.3.6

Conversation

@amiecorso

Copy link
Copy Markdown
Collaborator

What

Pin CI's Foundry to v1.3.6 (was floating nightly) and add make fmt / make fmt-check helpers.

Why

forge fmt output changes between Foundry versions, and CI used version: nightly — a moving target. Contributors on differing local Foundry versions produce formatting churn that pollutes diffs (e.g. unrelated call-wrapping changes) even when CI happens to pass. Pinning makes forge fmt --check deterministic.

v1.3.6 is the newest release under which main is already clean, so this PR reformats nothing and CI stays green on its own. (The formatter's call-wrapping behavior changed in v1.4.0.)

Changes

  • .github/workflows/test.yml: version: nightlyversion: "v1.3.6"
  • Makefile: make fmt / make fmt-check run the pinned version (installed side-by-side; your default Foundry is untouched)
  • CONTRIBUTING.md: formatting note

Follow-up

Feature branches should rebase on this and run make fmt so their diffs show only the real changes.

- test.yml: pin foundry-toolchain to v1.3.6 (was floating `nightly`)
- Makefile: add `fmt` / `fmt-check` using the pinned version
- CONTRIBUTING.md: document the formatting workflow

Co-authored-by: OpenCode <opencode-noreply@coinbase.com>
@cb-heimdall

Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
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 0
Sum 1

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