chore: release rain-erc 0.1.0

[thedavidmeister]

First stable publish to crates.io. Unblocks rain.metadata + rainlang publish chains.

Summary by CodeRabbit

• Chores
  • Version bumped to 0.1.0

[coderabbitai]

Walkthrough

Package version in Cargo.toml is incremented from 0.0.0 to 0.1.0. No dependencies, features, or other configuration settings are modified.

Changes

Package Version Update

Layer / File(s)	Summary
Version bump Cargo.toml	Crate version field updated from 0.0.0 to 0.1.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

🚥 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 'chore: release rain-erc 0.1.0' clearly and specifically describes the main change: bumping the crate version from 0.0.0 to 0.1.0 for a release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-05-23-publish-stable

---

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

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Cargo.toml`:
- Line 3: Cargo.toml's package version was bumped to "0.1.0" but Cargo.lock
still pins rain-erc at "0.0.0"; regenerate and commit an updated Cargo.lock so
the locked package version matches the crate version bump. Run cargo
generate-lockfile or cargo update (or cargo build) to refresh Cargo.lock, verify
the rain-erc entry now shows 0.1.0, and include the updated Cargo.lock in the
same PR.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: bc0b72d1-af51-4305-889e-3ec48a98b878

📥 Commits

Reviewing files that changed from the base of the PR and between af05442 and 7b94825.

📒 Files selected for processing (1)

• Cargo.toml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Sync Cargo.lock with the crate version bump.

After updating Cargo.toml at Line 3 to 0.1.0, Cargo.lock still pins rain-erc as 0.0.0 (see Cargo.lock snippet at lines 2459-2470). Please regenerate/update Cargo.lock in the same PR to avoid version drift during release and downstream reproducibility issues.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Cargo.toml` at line 3, Cargo.toml's package version was bumped to "0.1.0" but
Cargo.lock still pins rain-erc at "0.0.0"; regenerate and commit an updated
Cargo.lock so the locked package version matches the crate version bump. Run
cargo generate-lockfile or cargo update (or cargo build) to refresh Cargo.lock,
verify the rain-erc entry now shows 0.1.0, and include the updated Cargo.lock in
the same PR.

[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