Bump rain-deploy 0.1.7 -> 0.1.8

[thedavidmeister]

What

rain-deploy 0.1.7 -> 0.1.8, re-spelled at the single import site (test/abstract/RainlangExpressionDeployerDeploymentTest.sol, LibRainDeploy). Lockfile and remappings regenerated by forge soldeer update; the superseded rain-deploy-0.1.7/ line and dir pruned. No alias remapping.

Why

raindex imports rainlang-<v>/src/../test/abstract/OpTest.sol, which extends RainlangExpressionDeployerDeploymentTest, which spells rain-deploy-0.1.7/. raindex main pins rain-deploy 0.1.8 (#2865, Robinhood Chain + BNB Smart Chain) and Soldeer installs one version per package name, so with 0.2.4 installed raindex cannot resolve that import. The ruling on raindex is that mapping one version prefix onto another is not acceptable, so the fix is here, then a release; raindex #2863 pins the result.

Every other pin here already matches what raindex spells (forge-std 1.16.2, @openzeppelin-contracts 5.6.1, rain-solmem 0.1.28, rain-sol-codegen 0.1.36, rain-metadata 0.1.7, rain-lib-typecast 0.1.4, rain-math-float 0.2.1, rain-math-float-deploy 0.1.2, rainlang-interface 0.2.8, rain-string 0.2.0, rain-tofu-erc20-decimals 0.1.1, rain-intorastring 0.1.0, rain-lib-memkv 0.1.0, rain-math-binary 0.1.4, rain-extrospection 0.1.14), so nothing else moves.

rain-math-float-deploy 0.1.2 still spells rain-deploy-0.1.7/ in its RainDeploySuitesBase.sol; this repo only reaches its LibDecimalFloatDeploy.sol, whose import closure (ErrDecimalFloat, LibLogTable) never touches rain-deploy, so the bump compiles without a rain-math-float-deploy release.

QA

• Discriminating tests: n/a - pin bump and one import re-spelling; no behaviour is authored here. The gate is the full existing suite (unit + fork) on CI.
• Mutations applied: n/a - no logic line in the diff.
• Oracle: forge build exit 0 and forge fmt --check clean through the repo flake; LibRainDeploy.sol 0.1.7 -> 0.1.8 adds two chains and changes nothing the deployment test reads. Local full-suite result is in the first comment.
• Category check: pin bump only; the consumer-side change (raindex #2863) pins the release this produces.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V8ViHcKLVk2YoS2joH4HdN

Summary by CodeRabbit

• Chores
  • Updated the Rain Deploy dependency to version 0.1.8.
  • Updated related project references and test imports to use the new dependency version.

[thedavidmeister]

Local full suite on 6f86b1f through the repo flake, ARBITRUM_RPC_URL set for the fork tests: 225 suites, 1552 passed, 0 failed, 0 skipped.

[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: 3b617ea4-329f-4d93-af94-04b22627c505

📥 Commits

Reviewing files that changed from the base of the PR and between 7e47331 and 6f86b1f.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

• foundry.toml
• remappings.txt
• test/abstract/RainlangExpressionDeployerDeploymentTest.sol

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

---

📝 Walkthrough

Walkthrough

The PR updates the rain-deploy dependency from 0.1.7 to 0.1.8 in Foundry configuration, remappings, and a test import.

Changes

rain-deploy update

Layer / File(s)	Summary
Dependency version alignment foundry.toml, remappings.txt, test/abstract/RainlangExpressionDeployerDeploymentTest.sol	The dependency declaration, remapping, and LibRainDeploy import now reference rain-deploy version 0.1.8.

Priority: ⬇️ Low

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

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 6f86b

The dependency alignment is validated by the complete test suite, with no remaining merge-blocking risk identified.

🚥 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-deploy from version 0.1.7 to 0.1.8.
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-12-rain-deploy-0.1.8

---

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