Bump rain-math-binary 0.1.3 -> 0.1.4

[thedavidmeister]

Closes#125

Moves rain-math-binary from 0.1.3 to 0.1.4: foundry.toml, the soldeer.lock entry, and the four import sites that name the version — src/lib/parse/LibParseMeta.sol, src/lib/codegen/LibGenParseMeta.sol, test/src/lib/codegen/LibGenParseMeta.findExpander.t.sol, test/src/lib/codegen/LibGenParseMetaSlow.sol.

soldeer.lock was regenerated with forge soldeer update; the diff is 4 lines, the rain-math-binary entry alone — no other dependency moved.

No behaviour change

rain.math.binary/src/ has changed exactly once since 2024: 90244afc (2026-07-18), NatSpec on ctpop/ctpopSlow and a comment correction. So this is a version move, not a fix.

Why it matters downstream

This repo publishes rain-interpreter-interface, whose compiled src/ imports rain-math-binary — so the version named here is the one every consumer must supply through its own remappings. rainlang pins rain-interpreter-interface = 0.1.0, whose sources import rain-math-binary-0.1.1/, and the latest published rain-interpreter-interface (0.1.2) still pins 0.1.1. That is why rainlanguage/rainlang#551 cannot compile: no combination of currently published versions resolves.

Merging this is not enough on its own — a publishedrain-interpreter-interface release carrying 0.1.4 is what unblocks rainlang#551, which then bumps both pins in one commit.

QA

• Discriminating tests: n/a — a version string and four import paths changed, so there is no behaviour to discriminate. The existing suite is the regression check: 118 passed, 0 failed across 17 suites.
• Mutations applied: n/a — no source or test logic changed; there is no line whose behaviour a mutant could alter.
• Oracle: rain.math.binary's own history for the no-behaviour-change claim (git log -- src/ shows 90244afc as the only change since 2024), and soldeer.lock's checksum and integrity for the identity of the revision installed.
• Category check: Bump rain-math-binary 0.1.3 -> 0.1.4 #125 asks for the bump to 0.1.4; covered — foundry.toml, soldeer.lock and all four import sites. The publish that unblocks rainlang#551 is named above and is not part of this diff.

Summary by CodeRabbit

• Chores
  • Updated the Rain Math Binary dependency to version 0.1.4.
  • Refreshed related integrations and test references to maintain compatibility with the updated dependency.

[coderabbitai]

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: 26996f2d-79fb-4d54-9add-2977c605d60e

📥 Commits

Reviewing files that changed from the base of the PR and between aed67a6 and 9b90630.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (5)

• foundry.toml
• src/lib/codegen/LibGenParseMeta.sol
• src/lib/parse/LibParseMeta.sol
• test/src/lib/codegen/LibGenParseMeta.findExpander.t.sol
• test/src/lib/codegen/LibGenParseMetaSlow.sol

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

---

📝 Walkthrough

Walkthrough

The project updates its rain-math-binary dependency from 0.1.3 to 0.1.4 and aligns the production and test LibCtPop imports with the new versioned path.

Changes

Dependency upgrade

Layer / File(s)	Summary
Dependency version pin foundry.toml	The rain-math-binary dependency changes from 0.1.3 to 0.1.4.
Source and test import alignment src/lib/..., test/src/lib/codegen/*	Production and test LibCtPop imports now reference rain-math-binary-0.1.4.

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

Merge Risk:⚪ Minimal · up to 9b906

This change updates the dependency version references without changing product behavior, and no actionable merge-blocking risk remains beyond normal checks and review.

Possibly related issues

• rainlanguage/rain.extrospection issue 129 — Updates the same rain-math-binary dependency from 0.1.3 to 0.1.4 in another repository.
• rainlanguage/rainlang issue 556 — Coordinates related dependency pins and imports for the 0.1.4 upgrade.
• rainlanguage/rainlang.interface issue 123 — Modifies the same LibParseMeta.sol and LibGenParseMeta.sol versioned imports.

Possibly related PRs

• rainlanguage/rainlang.interface#119 — Updates the same dependency and corresponding LibCtPop imports from a previous version.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The summary shows the version pin and four imports, but it does not show the required remappings.txt update; soldeer.lock is excluded from review.	Update remappings.txt to 0.1.4 and verify soldeer.lock contains the regenerated 0.1.4 pin.

✅ Passed checks (4 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 dependency version bump, which is the main change.
Out of Scope Changes check	✅ Passed	All reported changes support the linked issue by updating rain-math-binary references from 0.1.3 to 0.1.4.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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-18-issue-125-bump-rain-math-binary

---

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

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

SIZE=S

_{You are interacting with an AI system.}