hash dep update

[thedavidmeister]

Motivation

Solution

Checks

By submitting this for review, I'm confirming I've done the following:

• made this PR as small as possible
• unit-tested any new functionality
• linked any relevant issues or PRs
• included screenshots (if this involves a front-end change)

Summary by CodeRabbit

• Chores

  • Updated internal library dependencies to latest versions

• Style

  • Minor code formatting improvement in storage operations

[coderabbitai]

Walkthrough

Updated three submodule pointers (forge-std, rain.lib.hash, rain.solmem) to reference newer commits. Applied minor formatting adjustment in LibMemoryKV.sol, converting multi-line assignment expression to single line. No functional changes introduced.

Changes

Cohort / File(s)	Summary
Submodule Updates lib/forge-std, lib/rain.lib.hash, lib/rain.solmem	Updated submodule commit pointers to newer versions. Changes are reference-only with no functional impact.
Code Formatting src/lib/LibMemoryKV.sol	Reformatted kv assignment in the set function from multi-line to single-line expression kv := or(...). No semantic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• flake lock #7 — Updates the same submodule pointers (forge-std, rain.solmem, rain.lib.hash) in parallel changes.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'hash dep update' is partially related to the changeset—it mentions hash dependency updates, which is addressed in lib/rain.lib.hash, but the changeset includes multiple unrelated updates: forge-std submodule, solmem submodule, and LibMemoryKV.sol formatting changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 2026-01-29-audit

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@lib/rain.lib.hash`:
- Line 1: The submodule lib/rain.lib.hash is pinned to a nonexistent commit
a4f6df6fb74b7d14d94fb8f0477888cc23616bc3; restore a valid ref by either
reverting the submodule change to the previous working commit or updating the
submodule entry to a commit/branch that exists upstream. Edit the submodule
reference (in .gitmodules and the gitlink for lib/rain.lib.hash) to point to a
valid upstream commit or switch the submodule to track a branch, then update the
submodule with git submodule sync && git submodule update --init --recursive to
verify the ref resolves.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check submodule status and the specific commit
git submodule status lib/rain.lib.hash 2>&1 || echo "Submodule check completed"
git -C lib/rain.lib.hash log -n 10 --oneline 2>&1 | head -20 || echo "No commit history available"
git -C lib/rain.lib.hash show a4f6df6fb74b7d14d94fb8f0477888cc23616bc3 --stat 2>&1 || echo "Cannot show commit"

Repository: rainlanguage/rain.lib.memkv

Length of output: 333

---

Revert or correct the submodule commit — the referenced commit does not exist in the upstream repository.

The submodule lib/rain.lib.hash is pinned to commit a4f6df6fb74b7d14d94fb8f0477888cc23616bc3, which is not found in the upstream repository (error: "not our ref"). This will break cloning and submodule initialization for all users. Either revert this change to a valid commit or update to the correct commit hash.

🤖 Prompt for AI Agents

In `@lib/rain.lib.hash` at line 1, The submodule lib/rain.lib.hash is pinned to a
nonexistent commit a4f6df6fb74b7d14d94fb8f0477888cc23616bc3; restore a valid ref
by either reverting the submodule change to the previous working commit or
updating the submodule entry to a commit/branch that exists upstream. Edit the
submodule reference (in .gitmodules and the gitlink for lib/rain.lib.hash) to
point to a valid upstream commit or switch the submodule to track a branch, then
update the submodule with git submodule sync && git submodule update --init
--recursive to verify the ref resolves.