chore(creact): 0.5.1

[drn1996]

Bumps @creact-labs/creact to 0.5.1 so the store hydration fix in #20 can ship.

Patch, per the release flow in .github/workflows/release.yml: land on develop, bump the package's own version there, then develop → release publishes.

What ships in it

#20 — a store is restored by its node's own path rather than its parent's. prepareHydration keyed each store by node.path.slice(0, -1), so two keyed siblings shared one hydration entry and every one of them restored whichever was persisted last. Persistence was already correct; only the restore lookup discarded the segment that made them distinct.

The practical effect: a component rendered per item in a <For> can own a createStore again, instead of per-entity state having to live in outputs to dodge the collision.

Order

Merge #20 first, then this — or this first and #20 after; the version only has to be right on develop before the release PR is cut.

[coderabbitai]

Warning

Review limit reached

@drn1996, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2f5c733a-b3c9-4383-b274-41adcea02b46

📥 Commits

Reviewing files that changed from the base of the PR and between f1006fc and 4230c78.

📒 Files selected for processing (1)

• packages/creact/package.json

---

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]

🤖 Grok fallow review — proceed

No dead code, duplication, above-threshold functions, audit metrics, or change-attributed advisories. Non-gating hotspot movement noted; release may proceed.

• Hotspot accelerating: packages/create-creact-app/src/index.ts (63.3, 6 commits, 235 churn)
• Hotspot accelerating: packages/testing/src/wait-for.ts (60.7, 6 commits, 159 churn)
• Hotspot accelerating: packages/creact/src/reactive/array.ts (26.1, 3 commits, 633 churn)
• Hotspot accelerating: packages/creact/src/reactive/selector.ts (23.4, 3 commits, 35 churn)
• Hotspot accelerating: packages/create-creact-app/src/templates.ts (6.8, 7 commits, 365 churn)
• Hotspot accelerating: packages/creact/src/runtime/fiber.ts (1.4, 3 commits, 107 churn)
• Repository health score 82 B with deductions from hotspots (-10.0), unit size (-4.7), dead files (-1.7), coupling (-1.3); dead files 8.3%

_{Reviews the full fallow report — dead code, duplication, health, and audit. Re-runs edit this comment.}