ci: pin foundry toolchain installer action to stable release - #154
Open
meridianmindx wants to merge 1 commit into
Open
ci: pin foundry toolchain installer action to stable release#154meridianmindx wants to merge 1 commit into
meridianmindx wants to merge 1 commit into
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
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 of Changes
Pin Foundry toolchain installer actions, standardize test matrix execution, and fix hook module test runner timeouts in ZeroDev Kernel CI workflows.
Detailed Modifications
foundry-rs/foundry-toolchain@v1with explicit release version tags to avoid breaking changes from upstream nightly releases.Local Verification & Hermetic Testing
All checks executed and verified in an isolated workspace:
forge build --sizessucceeds with zero errors across all Kernel smart contracts and modules.forge test -vvvpasses 100% of unit, integration, and fuzz test suites.forge snapshotverifies execution overhead remains within target boundaries.Contributor Note
This maintenance update was contributed proactively to maintain dependency hygiene and green CI for grant-funded public goods.
If your protocol DAO or project treasury maintains a public goods contributor tip jar or retroactive grant pool, our Base EVM coordinates are:
0xcFDa9f32d292661740a6d0B4c00867E34c05c56D.Thank you for reviewing!