fix(audit-low): close 2 hazard-surface findings#233
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
d0ffec9 to
d92e9a6
Compare
90b10ce to
48e95fd
Compare
48e95fd to
1fa5fb4
Compare
05fbb57 to
b8563f9
Compare
1fa5fb4 to
8619624
Compare
b8563f9 to
792a663
Compare
8619624 to
71f2411
Compare
71f2411 to
dae71e5
Compare
792a663 to
6ec3ba4
Compare
- #146 CONFIG-SUBMODULE-LOCK: regenerate foundry.lock to align with the working-tree pointer for lib/st0x.deploy (99552486...). Prior state had foundry.lock pinned to 766b468f... while .gitmodules resolved to 99552486..., producing a build warning on every nix invocation. The working-tree pointer is what the code is actually compiled against, so the lock is updated to match it (not the other way around). - #214 HAZARD-CROSS-FILE-SYNC: add .github/workflows/suite-names-sync.yaml (Option B in the issue — the simpler fence). The workflow extracts the deployment-suite names from script/Deploy.sol's keccak256("...") preimages and compares them against the operator-facing dropdown's options: list in .github/workflows/manual-sol-artifacts.yaml. If the two lists diverge, CI fails with a diff and a hint pointing at both files. This catches both typos and missing-entry drift in the same PR that introduces them, instead of at deploy time as a "Unknown deployment suite" revert. Chosen over Option A (generated source of truth) because it ships in one workflow file with no new build step, no jq dependency, and the existing duplication in Deploy.sol stays readable as plain Solidity. forge build no longer warns about the revision mismatch. nix CI green (forge fmt no-op, rainix-sol-static clean, rainix-sol-legal clean, 169 tests pass under the standard --no-match-contract exclusions). Closes #146, #214. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
dae71e5 to
5bdbd3f
Compare
6ec3ba4 to
1cc1c91
Compare
|
Deferred for Euler launch. The foundry.lock alignment is moot post-soldeer; the suite-names CI drift check is non-blocking. |

the working-tree pointer for lib/st0x.deploy (99552486...). Prior
state had foundry.lock pinned to 766b468f... while .gitmodules
resolved to 99552486..., producing a build warning on every nix
invocation. The working-tree pointer is what the code is actually
compiled against, so the lock is updated to match it (not the
other way around).
(Option B in the issue — the simpler fence). The workflow extracts the
deployment-suite names from script/Deploy.sol's keccak256("...")
preimages and compares them against the operator-facing dropdown's
options: list in .github/workflows/manual-sol-artifacts.yaml. If the
two lists diverge, CI fails with a diff and a hint pointing at both
files. This catches both typos and missing-entry drift in the same
PR that introduces them, instead of at deploy time as a "Unknown
deployment suite" revert. Chosen over Option A (generated source of
truth) because it ships in one workflow file with no new build
step, no jq dependency, and the existing duplication in Deploy.sol
stays readable as plain Solidity.
forge build no longer warns about the revision mismatch. nix CI green
(forge fmt no-op, rainix-sol-static clean, rainix-sol-legal clean, 169
tests pass under the standard --no-match-contract exclusions).
Closes #146, #214.
Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com