Uh oh!
There was an error while loading. Please reload this page.
fix(package.json): use HTTPS repository URL instead of SSH - #83
Conversation
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Walkthrough将 Changes仓库地址协议更新
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Code Review
This pull request updates the repository URL in package.json from an SSH-based git URL to an HTTPS URL. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
nrps9909
left a comment
There was a problem hiding this comment.
Approved exact head 26b66d0212f2e17dcc1d6647b281c55210ed587b. The package metadata parses with the expected HTTPS repository URL, git ls-remote https://github.com/react-component/textarea.git HEAD resolves to the current upstream head, and the exact one-line diff passes git diff --check. The failed workflow is unrelated: compile reaches the repository-wide deep-import rule and reports the eight pre-existing @rc-component/input/lib/* and @rc-component/util/lib/* imports on the unchanged base; this PR only changes package.json.
Problem
The published package metadata for
rc-textarea(latest1.10.2) and the sourcepackage.jsonuse an SSH-style GitHub repository URL:The repository is public, so npm consumers and tooling should be able to follow the repository link over HTTPS without SSH/GitHub key setup. SSH URLs can break
npm repo, provenance tooling, and automated source links for users without SSH keys configured.Fix
Use the HTTPS form, consistent with most react-component packages:
One-line change, no functional impact.
Summary by CodeRabbit
发版说明