chore(deps): bump rain-lib-typecast 0.1.0 -> 0.1.4, rain-sol-codegen 0.1.0 -> 0.1.36

[thedavidmeister]

Clears the two stale deps in one PR:

• rain-lib-typecast 0.1.0 -> 0.1.4
• rain-sol-codegen 0.1.0 -> 0.1.36 (the version raindex uses on main, so the API is proven in-org)

Mechanics: versions bumped in foundry.toml, soldeer.lock regenerated via forge soldeer update, and every versioned import path rewritten (rain-lib-typecast-0.1.0/ -> -0.1.4/, rain-sol-codegen-0.1.0/ -> -0.1.36/). remappings.txt is gitignored and regenerated by soldeer in CI.

Transitive forge-std bump (disclosed): rain-sol-codegen 0.1.36 hard-pins forge-std-1.16.2/src/Vm.sol in vendored src this repo compiles (LibCodeGen.sol, LibHexString.sol). With recursive_deps = false those imports resolve through this repo's remappings, so forge-std moves 1.16.1 -> 1.16.2 in the same clean bump: foundry.toml, soldeer.lock, and this repo's 12 forge-std imports rewritten. No alias remappings, no second forge-std copy. The only vendored files still spelling forge-std-1.16.1/ are dep-internal test files this repo never compiles.

.gas-snapshot left untouched: no CI job checks it, and the solmem bump merged yesterday (#130) set the same precedent for dep bumps.

Verified locally in the repo's #sol-shell: forge build clean, forge test -vvv full suite 118 passed / 0 failed / 0 skipped.

QA

• Discriminating tests: n/a - dependency version bump only, no behavior authored; the gate is the existing full suite, which passed against the bumped deps (118 passed / 0 failed / 0 skipped in #sol-shell)
• Mutations applied: n/a - the diff contains no logic lines to mutate; it is version strings in foundry.toml/soldeer.lock and versioned import path rewrites only
• Oracle: n/a - no new expected values introduced; the existing suite's own oracles are unchanged and all still pass
• Category check: directive asks (A) rain-lib-typecast 0.1.0->0.1.4 and (B) rain-sol-codegen 0.1.0->0.1.36 in ONE PR; covered A,B, plus the disclosed transitive forge-std 1.16.1->1.16.2 that codegen 0.1.36's vendored src forces

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Updated development and testing tools to newer versions.
  • Refreshed supporting libraries used for type casting and code generation.
  • Updated project references to maintain compatibility with the latest toolchain versions.

• Tests

  • Updated test tooling references without changing test coverage or behavior.

[coderabbitai]

Warning

Review limit reached

@thedavidmeister, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7bee7c79-1c57-45ff-be15-aca58f31c7b8

📥 Commits

Reviewing files that changed from the base of the PR and between c010881 and bf87122.

📒 Files selected for processing (1)

• slither.config.json

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: d6115e2d-a9d7-42f4-9c90-b1b9249fe3d3

📥 Commits

Reviewing files that changed from the base of the PR and between 99eaa20 and c010881.

⛔ Files ignored due to path filters (1)

• soldeer.lock is excluded by !**/*.lock

📒 Files selected for processing (14)

• foundry.toml
• src/lib/codegen/LibGenParseMeta.sol
• test/abstract/BytecodeTest.sol
• test/lib/bloom/LibBloom.t.sol
• test/src/lib/bytecode/LibBytecode.sourceCount.t.sol
• test/src/lib/caller/LibContext.hash.t.sol
• test/src/lib/caller/LibContext.t.sol
• test/src/lib/caller/LibContextSlow.sol
• test/src/lib/caller/LibEvaluable.t.sol
• test/src/lib/codegen/LibGenParseMeta.buildMeta.t.sol
• test/src/lib/codegen/LibGenParseMeta.findExpander.t.sol
• test/src/lib/ns/LibNamespace.t.sol
• test/src/lib/parse/LibParseMeta.lookupWord.t.sol
• test/src/lib/parse/LibParseMeta.wordBitmapped.t.sol

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The project updates dependency pins for forge-std, rain-lib-typecast, and rain-sol-codegen. Source and test imports now reference those versions.

Changes

Dependency alignment

Layer / File(s)	Summary
Update dependency pins foundry.toml	Updates forge-std to 1.16.2, rain-lib-typecast to 0.1.4, and rain-sol-codegen to 0.1.36.
Align Solidity imports src/lib/codegen/LibGenParseMeta.sol, test/abstract/BytecodeTest.sol, test/lib/bloom/LibBloom.t.sol, test/src/lib/bytecode/*, test/src/lib/caller/*, test/src/lib/codegen/*, test/src/lib/ns/*, test/src/lib/parse/*	Updates Solidity imports to use the configured dependency versions. No contract logic or test behavior changes.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: ⚪ Minimal · up to c0108

This PR updates dependency versions and their import paths, including the required forge-std transitive update, without authored logic changes. The full test suite passes, and no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the two primary dependency upgrades and matches the pull request changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (14 skipped: 14 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-08-22-typecast-0-1-4-codegen-0-1-36

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

• Simple bug fixes, typos, or minor refactoring
• Single-purpose changes affecting 1-2 files
• Documentation updates
• Configuration tweaks
• Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

• Fix typo in variable name
• Update README with new instructions
• Adjust configuration values
• Simple one-line bug fixes
• Import statement cleanup

Medium (M)

Characteristics:

• Feature additions or enhancements
• Refactoring that touches multiple files but maintains existing behavior
• Breaking changes with backward compatibility
• Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

• Add new feature or component
• Refactor common utility functions
• Update dependencies with minor breaking changes
• Add new component with tests
• Performance optimizations
• More complex bug fixes

Large (L)

Characteristics:

• Major feature implementations
• Breaking changes or API redesigns
• Complex refactoring across multiple modules
• New architectural patterns or significant design changes
• Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

• Complete new feature with frontend/backend changes
• Protocol upgrades or breaking changes
• Major architectural refactoring
• Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

• Test coverage impact: More comprehensive test changes lean toward larger classification
• Risk level: Changes to critical systems bump up a size category
• Team familiarity: Novel patterns or technologies increase complexity

Notes:

• the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
• the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
• do not include any additional text, only the size classification
• your assessment comment must not include tips or additional sections
• do NOT tag me or anyone else on your comment