release: 0.1.3 - #34
Conversation
`DecimalFloat` moved to 0xEc632ea4D04A6D72F87E60FEb4C6B6813cda59bd when `agree` was added to the concrete. It is now deployed and source-verified on all nine supported networks, so the pins are freezable. `cutRelease()` froze `src/generated/0_1_3/` from the rolling candidate and regenerated the released-suites libs, which now carry 0_1_3 beside 0_1_2. `LogTables` is unchanged at 0xc51a14251b0dcF0ae24A96b7153991378938f5F5 — its bytes did not move — and is frozen again under this tag because a release record names every suite it releases. Also corrects the optimizer note, which named ZOLTU_DEPLOYED_DECIMAL_FLOAT_ADDRESS as 0x799632d2… and DECIMAL_FLOAT_CONTRACT_HASH as 0xdc4688…. Both are from before the address moved; the committed pins are 0xEc632ea4… and 0x0d43af49…. `forge test --force`: 42 suites, 85 tests, 82 passed, 3 failed on missing `*_RPC_URL` as always. fmt and lint clean. Tag `sol-v0.1.3` after this merges; `package-release.yaml` publishes from it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe package version and documented DecimalFloat deployment data are updated to 0.1.3. The released suite registries now include frozen 0.1.3 artifacts for DecimalFloat and LogTables. Changes0.1.3 release registry
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~8 minutes Change: Other Merge Risk: ⚪ Minimal · up to The 0.1.3 release metadata and suite catalogs match the frozen artifacts; no merge-blocking issue is evident. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 2 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
DecimalFloatmoved to0xEc632ea4D04A6D72F87E60FEb4C6B6813cda59bdwhenagreewas added to the concrete. It is now deployed and source-verified on all nine networks, so the pins are freezable.cutRelease()frozesrc/generated/0_1_3/from the rolling candidate and regenerated the released-suites libs, which now carry0_1_3beside0_1_2.LogTablesis unchanged at0xc51a14251b0dcF0ae24A96b7153991378938f5F5and is frozen again under this tag, because a release record names every suite it releases.Also corrects the optimizer note, which named the address as
0x799632d2…and the codehash as0xdc4688…. Both predate the move; the committed pins are0xEc632ea4…and0x0d43af49….Tag
sol-v0.1.3after merge —package-release.yamlpublishes from it.QA
DecimalFloatDeploySnapshotTest's inherited frozen-record walk andtestSuitesLiveOnEverySupportedNetwork— the latter asserts every frozen release is live with the code it froze, so0_1_3naming an address that is not deployed fails it. It needs*_RPC_URL, so CI is where it runs.cutRelease()refuses the mutations that matter. Freezing a version already frozen revertsSnapshotAlreadyFrozen, and an empty rolling snapshot revertsNothingToFreeze;checkReleaseFollowsRecordrejects a tag out of order.eth_getCodeanswers for and the prod walk checked green on main atcca9aab7, not values this repo asserts about itself.DecimalFloatpin. Not covered: the tag push itself, which follows this merge.🤖 Generated with Claude Code
Summary by CodeRabbit