Bump rain-math-saturating 0.1.1 -> 0.1.2

[thedavidmeister]

Small dependency bump: rain-math-saturating 0.1.1 -> 0.1.2 (latest published).

• foundry.toml: version bumped.
• soldeer.lock: regenerated with forge soldeer update — only the saturating entry changed.
• test/lib/LibFixedPointDecimalScaleSlow.sol: versioned import path moved to rain-math-saturating-0.1.2/.
• remappings.txt: pruned by hand (soldeer appends, never prunes) — removed the old rain-math-saturating-0.1.1/ entry and a pre-existing stale rain-string-0.1.0/ line that pointed at a dependency directory that no longer exists (nothing in src/test/dependencies references it).

0.1.2 still ships src/lib/LibSaturatingMath.sol at the same path; the vendored source uses only relative imports, so no remapping walls.

Local gate: forge build clean, forge test 78/78 passed.

QA

• Discriminating tests: n/a — dependency version bump only; no behavior of this repo changes, so there is no new behavior to discriminate. Full existing suite run as the gate: 78/78 passed locally (forge test via rainix devshell), including the saturating parity/reference tests that exercise the bumped dependency.
• Mutations applied: n/a — the diff contains no logic: version pins (foundry.toml), regenerated lockfile (soldeer.lock), remapping prune, and a versioned import path move. No mutable statements were added or changed.
• Oracle: n/a — no new expected values introduced; the existing suite's oracles (including LibFixedPointDecimalScaleSlow reference implementations that import the bumped package) are unchanged and still pass.
• Category check: maintenance dep bump per user directive to clear stale deps; not tied to a GitHub issue.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated the underlying mathematical calculation library to the latest maintenance release.
  • Removed an obsolete configuration mapping.
  • No user-facing features or behavior were changed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 6fef20a8-37c4-4e63-9364-0466a18cf9d8

📥 Commits

Reviewing files that changed from the base of the PR and between 154c471 and e4c698c.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

• foundry.toml
• remappings.txt
• test/lib/LibFixedPointDecimalScaleSlow.sol

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

---

Walkthrough

The pull request updates rain-math-saturating from version 0.1.1 to 0.1.2 in Foundry configuration, remappings, and a test import. It also removes the obsolete rain-string-0.1.0 remapping.

Changes

Dependency update

Layer / File(s)	Summary
Synchronize dependency references foundry.toml, remappings.txt, test/lib/LibFixedPointDecimalScaleSlow.sol	The project uses rain-math-saturating version 0.1.2 in its dependency declaration, remapping, and test import. The obsolete rain-string-0.1.0 remapping is removed.

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

Merge Risk: ⚪ Minimal · up to e4c69

This change updates the saturating-math dependency and its references without changing repository behavior; the existing build and test suite pass, so no actionable merge-blocking risk remains.

🚥 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: upgrading rain-math-saturating from version 0.1.1 to 0.1.2.
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. (3 skipped: 3 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

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-rain-math-saturating-0.1.2

---

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