release: rain-deploy 0.1.15

[thedavidmeister]

The release commit for rain-deploy 0.1.15. It carries no source change over 0.1.14 — both frozen records are byte-identical, so every pin a consumer reads is the same.

Why a second version

sol-v0.1.14 passed release-guard and then failed inside the suite the publish job runs: rpc.mainnet.chain.robinhood.com answered 403 under 32 parallel forks, taking 13 tests with it while 655 passed (run). Nothing reached Soldeer.

The endpoint is not broken for ordinary use — from one host the same hour it answered curl (including a 32-way concurrent burst, 32/32) and cast chain-id. It fails only under the fork load a real suite produces, which is why no probe saw it coming. rainix #406 drops it to last behind tenderly and publicnode; #407 corrects the reason recorded next to it.

A tag is the only release trigger and a published tag is not re-pushed, so the retry has to be a new version rather than a re-run.

QA

• Discriminating tests: n/a with reason — no hand-authored source in the diff. Content is generator output from forge script script/Build.sol --sig 'cutRelease()'; the existing record tests (GeneratedSnapshotShape.t.sol, BuildRecordRoot.t.sol, BuildScript.t.sol, Build.t.sol) are what discriminate it.
• Mutations applied: n/a with reason — a version line plus generated files. The generator is untouched: no file under src/abstract/, src/lib/LibRainDeploySnapshot.sol or script/ is in the diff.
• Oracle: release-guard for what the tagged commit must carry (version identity, record present in HEAD), and 0.1.14's own release commit for the diff shape, which this matches file-for-file.
• Category check: the task is a publishable release commit on a working RPC order. Covered: bump to 0.1.15, src/generated/0_1_15/ frozen, released-suites libs at 7 entries, monotonicity satisfied, and the RPC cause fixed upstream rather than worked around in this repo. Verified: 0_1_15/ is byte-identical to 0_1_14/ and to the committed candidate/, so the freeze introduced no drift. Deliberately not done — re-running sol-v0.1.14 (hook-blocked, and a tag is the trigger), and setting a RPC_URL_ROBINHOOD_FORK secret for this repo alone (none is set at repo or org level; the fix belongs in the shared table).
• Checks: forge test 668 passed / 0 failed with robinhood bound to tenderly; the same tree was 655/13 against the official endpoint, which is the failure reproduced locally. forge fmt --check clean.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • Added release 0.1.15 to the available AddressRegistry and MigrationRegistry suites.
  • Existing releases remain available alongside the new release.
  • Updated the published package version to 0.1.15, aligning package metadata with the newly available release. This update makes the latest release selectable through both registries while preserving access to the six previously listed suites.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 9d862842-112a-4020-9f3a-9d2ed0fc801c

📥 Commits

Reviewing files that changed from the base of the PR and between 72ff06b and d525b11.

⛔ Files ignored due to path filters (2)

• src/generated/0_1_15/AddressRegistry.sol is excluded by !**/generated/**
• src/generated/0_1_15/MigrationRegistry.sol is excluded by !**/generated/**

📒 Files selected for processing (3)

• foundry.toml
• src/lib/LibAddressRegistryReleased.sol
• src/lib/LibMigrationRegistryReleased.sol

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

---

Walkthrough

The external package version changes from 0.1.14 to 0.1.15. The AddressRegistry and MigrationRegistry released-suite lists each add a 0.1.15 entry.

Changes

Release 0.1.15

Layer / File(s)	Summary
Update release version and suite registrations foundry.toml, src/lib/LibAddressRegistryReleased.sol, src/lib/LibMigrationRegistryReleased.sol	The external package version changes to 0.1.15. Both released-suite lists add a seventh entry using the 0.1.15 deployment metadata. The existing six entries remain unchanged.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other

Suggested reviewers: claude

Merge Risk: ⚪ Minimal · up to d525b

The 0.1.15 release metadata is consistent with the repository’s frozen-release records. Available evidence does not establish that the reported RPC failures block this release.

🚥 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 identifies the rain-deploy 0.1.15 release, which matches the version bump and release metadata changes.
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)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.}

[linear]

RAI-2980