Skip to content

fix: update ckb-tui download URL to nervosnetwork org repo - #489

Merged
RetricSu merged 1 commit into
developfrom
agent/claude-bear/e5521a71
Aug 3, 2026
Merged

fix: update ckb-tui download URL to nervosnetwork org repo#489
RetricSu merged 1 commit into
developfrom
agent/claude-bear/e5521a71

Conversation

@humble-little-bear

Copy link
Copy Markdown
Collaborator

ckb-tui has been transferred from the personal repo Officeyutong/ckb-tui to the org repo nervosnetwork/ckb-tui. As a downstream consumer, offckb's installer needs to download release assets from the new location.

Changes

  • src/tools/ckb-tui.ts: point the release download URL at nervosnetwork/ckb-tui (the only hardcoded reference to the old repo in the codebase)
  • Added a patch changeset

Verification

  • Confirmed via the GitHub API that all releases (v0.1.0–v0.1.4) moved with the transfer and every asset digest matches the digests pinned in KNOWN_SHA256 byte-for-byte, so the fail-closed checksum gate still passes
  • Downloaded ckb-tui-with-node-linux-amd64.tar.gz (v0.1.4) from the new URL: SHA-256 eaed2cfb…01cbd matches the pinned digest exactly
  • tsc --noEmit clean; full jest suite green (36 suites, 310 passed / 7 skipped)

The historical Officeyutong/ckb-tui#13 reference in CHANGELOG.md is intentionally left as-is (released changelog entries are historical records, and GitHub redirects transferred repo links).

🤖 Generated with Claude Code

ckb-tui transferred from the personal repo Officeyutong/ckb-tui to the
org repo nervosnetwork/ckb-tui. Point the installer at the new release
download URL. The release assets moved with the transfer, so the pinned
SHA-256 digests in KNOWN_SHA256 still match (verified against the GitHub
API and a live download of the v0.1.4 linux-amd64 asset).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@humble-little-bear, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: a07b4201-f7a8-4351-b9e3-abef1cc906c7

📥 Commits

Reviewing files that changed from the base of the PR and between 51f437e and 5ca77f4.

📒 Files selected for processing (2)
  • .changeset/ckb-tui-org-repo-url.md
  • src/tools/ckb-tui.ts

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

Comment @coderabbitai help to get the list of available commands.

@RetricSu
RetricSu merged commit a591136 into develop Aug 3, 2026
7 checks passed
@RetricSu
RetricSu deleted the agent/claude-bear/e5521a71 branch August 3, 2026 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants