Bump rain-sol-codegen to 0.1.37

[thedavidmeister]

What

Bump the rain-sol-codegen soldeer pin from 0.1.36 to 0.1.37 in foundry.toml and soldeer.lock, and rewrite the single import in src/lib/codegen/LibGenParseMeta.sol to the new versioned remapping. No other package pins are touched and no API adaptation was needed.

Why

The org health dashboard flags the 0.1.36 pin as stale; 0.1.37 is the latest published revision on the soldeer registry.

QA

• Discriminating tests: n/a, pure pin bump with no logic change; the existing suite compiled against 0.1.37 and passed 128/128 locally.
• Mutations applied: n/a, no logic changed.
• Oracle: soldeer registry latest revision (0.1.37); git diff scope is foundry.toml, soldeer.lock and one import path string.
• Category check: dependency bump. Note that forge build --deny warnings fails locally on 37 pre-existing forge lint warnings in src/lib/parse/LibParseMeta.sol and test files that this diff does not touch; compilation itself succeeds.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V8ViHcKLVk2YoS2joH4HdN

Summary by CodeRabbit

• Chores
  • Updated the code generation package to version 0.1.37.
  • Aligned the application’s code generation integration with the updated package version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 5e5eb8f8-3d54-4bca-90f7-5c609033966b

📥 Commits

Reviewing files that changed from the base of the PR and between 76c1a30 and c98693d.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• foundry.toml
• src/lib/codegen/LibGenParseMeta.sol

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

---

📝 Walkthrough

Walkthrough

The project updates rain-sol-codegen from version 0.1.36 to 0.1.37 in the dependency declaration and the LibCodeGen import path.

Changes

Codegen dependency update

Layer / File(s)	Summary
Dependency and import update foundry.toml, src/lib/codegen/LibGenParseMeta.sol	The dependency declaration and LibCodeGen import path now reference rain-sol-codegen version 0.1.37.

Priority: ⬇️ Low

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

Change: Other

Suggested reviewers: dcatki

Merge Risk: ⚪ Minimal · up to c9869

This dependency update is consistent and validated by the existing test suite, so it is ready to merge.

🚥 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 and concisely describes the main change: updating rain-sol-codegen to version 0.1.37.
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…
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

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-09-13-codegen-0-1-37

---

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