chore(deps): bump io to v0.15.4, and cli onto the render tag it ships beside

[Snider]

Every dappco.re pin in both modules was already on its latest published tag but two. This is those two.

module	pin	from	to
go/	dappco.re/go/io	v0.15.3	v0.15.4
cli/	dappco.re/go/io	v0.15.3	v0.15.4
cli/	dappco.re/go/render	v0.20.0	v0.20.2

The render pin is the one worth a sentence. cli is a sibling module, not a consumer of somebody else's library, and it was pinned two patches behind the tag its own repository had already published — go/v0.20.2 is main's current head. A binary built from this tree was testing against a library that is not the library the tree contains.

Direct-version go get then tidy. No replace directives anywhere.

Checked rather than assumed — everything else is already at latest: go v0.12.0, cli v0.13.0, config v0.18.0, i18n v0.12.1, ts v0.2.2, webview v0.11.0, log v0.13.1, scm v0.22.0, process v0.16.1.

Receipts

cd go  && GOWORK=off go build ./...   exit 0
          GOWORK=off go vet   ./...   exit 0
          GOWORK=off go test  ./...   exit 0, 58 packages ok
cd cli && GOWORK=off go build ./...   exit 0
          GOWORK=off go vet   ./...   exit 0
          GOWORK=off go test  ./...   exit 0
gofmt -l   0 offenders in both modules
GOOS=js GOARCH=wasm go build ./cli/wasm/
          2.20 MB raw (gate 3.5)   0.65 MB gzip (gate 1.0)

🤖 Generated with Claude Code
Co-Authored-By: Virgil virgil@lethean.io

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 46 minutes

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: f4a862bc-fef5-44fc-ac4b-d123ea5f8c06

📥 Commits

Reviewing files that changed from the base of the PR and between 5ac292a and 4f4a5c9.

⛔ Files ignored due to path filters (2)

• cli/go.sum is excluded by !**/*.sum
• go/go.sum is excluded by !**/*.sum

📒 Files selected for processing (2)

• cli/go.mod
• go/go.mod

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

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