Generate ABI package with Foundry - #2985
Open
clement-ux wants to merge 3 commits into
Open
Conversation
clement-ux
requested review from
naddison36,
shahthepro and
sparrowDom
as code owners
August 25, 2026 15:08
This was referenced Aug 25, 2026
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.
Why
After #2983, Hardhat was no longer testing or deploying contracts. One dependency remained in the ABI release path:
@origin/defiwas still built from Hardhat compilation artifacts.This PR moves that last compilation step to Foundry without changing the package consumed by applications.
Before and after
Before:
After:
The compatibility exporter reads Foundry output and writes the same public artifact shape used by the existing package. Consumers keep the same filenames, contract/source identities and ABI entries.
What changes
forge build contracts/ -j 1@origin/defipackage formatTalos and Hardhat
Talos is unchanged. It continues to use
deployments/**, the task ABI files and its standalone action runner. Its action registry loads without skipped actions, and all task tests pass.Hardhat also remains available as the operational task CLI. It is simply no longer part of contract testing, deployment or ABI compilation.
Stack
This PR is intentionally based on #2983:
Validation
npm pack --dry-run --json:@origin/defiwith 292 ABI filespnpm run test:tasks: 22 passingpnpm run test:scripts: 66 passingpnpm run test:layouts: 11 passinggit diff --checkpass