Files
liquid/foundry.lock
zeekayandHanzo Dev ca677b3aaf CI measures the bytecode that ships
forge build --sizes ran under FOUNDRY_PROFILE=ci, and Liquid clears EIP-170
only with the via_ir and yul settings the production profile carries. The gate
was measuring a contract that never deploys.

Test selection now lives in one place the Makefile and the workflows both read,
so a green laptop and a green CI mean the same thing. Invariants are seeded, so
a reported counterexample reproduces. Each scanner stops the build at the
threshold CI uses -- a scanner that cannot fail reports nothing.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-27 15:28:43 -07:00

27 lines
702 B
Plaintext

{
"lib/chainlink-brownie-contracts": {
"rev": "5cb41fbc9b525338b6098da5ea7dd0b7e92f89e4"
},
"lib/forge-std": {
"rev": "8bbcf6e3f8f62f419e5429a0bd89331c85c37824"
},
"lib/halmos-cheatcodes": {
"rev": "6da4e692c357ba6d641a2e677a28298cac9f76ab"
},
"lib/openzeppelin-contracts": {
"rev": "483fc3f1f89ef6eb0803d578a4a17346d94359f7"
},
"lib/openzeppelin-contracts-upgradeable": {
"rev": "56118009a30763d6b635676bed7968874036bb53"
},
"lib/permit2": {
"rev": "cc56ad0f3439c502c246fc5cfcc3db92bb8b7219"
},
"lib/solmate": {
"rev": "97bdb2003b70382996a79a406813f76417b1cf90"
},
"lib/vault-v2": {
"rev": "2f0c4a3885160371369362f624d2a6e9c94c399a"
}
}