Bump rain-sol-codegen 0.1.37, rainlang-interface 0.2.9, rain-deploy 0.1.10, rainlang 0.2.6 and the float/metadata/typecast pins they force - #215
Conversation
….1.10, rainlang 0.2.6, rain-math-float 0.2.1, rain-metadata 0.1.7, rain-lib-typecast 0.1.4, add rain-math-float-deploy 0.1.2 rainlang 0.2.6 hard-imports rain-math-float 0.2.1, rain-math-float-deploy 0.1.2, rain-metadata 0.1.7 and rain-lib-typecast 0.1.4, and soldeer keeps one version per package, so those pins move with it. Old copies under dependencies/ and stale remappings are pruned; no version is aliased. flake.lock takes rain.cli 91d70ac so the devshell vendors crates again. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V8ViHcKLVk2YoS2joH4HdN
ℹ️ 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 (21)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe change updates Rain dependency versions in Foundry configuration and remappings. It updates matching imports in build scripts, deployment scripts, production Solidity files, and tests. No runtime logic, public declarations, test logic, or assertions change. ChangesRain dependency updates
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to The PR updates aligned Rain dependency versions and imports without changing application logic or test assertions; no concrete runtime or integration regression is established, so it is suitable to merge after normal build checks. 🚥 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 |
What
Bump rain-sol-codegen 0.1.36 -> 0.1.37 and the pins that carry it: rainlang-interface 0.2.8 -> 0.2.9, rain-deploy 0.1.7 -> 0.1.10, rainlang 0.2.1 -> 0.2.6.
rainlang 0.2.6 hard-imports versioned paths that the repo did not pin at those versions, and soldeer keeps one version per package, so the bump forces: rain-math-float 0.1.1 -> 0.2.1, rain-metadata 0.1.0 -> 0.1.7, rain-lib-typecast 0.1.0 -> 0.1.4, and a new pin rain-math-float-deploy 0.1.2. Every old copy under dependencies/ and every stale remappings.txt line is pruned; no version is aliased onto another. Versioned import paths across src, script and test are rewritten to match.
flake.lock: the rain input (github:rainlanguage/rain.cli) moves to 91d70ac, the commit that fixed crate vendoring, so the repo devshell builds again.
Why
The org health dashboard flags the pins as stale. Published packages hard-import the versioned codegen path, so the repo can only take codegen 0.1.37 once every pinned package that imports codegen is on a release built against it.
QA
Discriminating tests: n/a, pure pin bump with no logic changed; the existing suite is the check.
Mutations applied: n/a, no logic changed.
Oracle: soldeer registry latest revisions for each package and the versioned imports inside the fetched packages; git diff scope is foundry.toml, soldeer.lock, remappings.txt, flake.lock, import lines and the regenerated pointer.
Category check: dependency bump.
🤖 Generated with Claude Code
https://claude.ai/code/session_01V8ViHcKLVk2YoS2joH4HdN
Summary by CodeRabbit
Chores
Tests