chore(deps): upgrade @pkcprotocol/pkc-js 0.0.82 -> 0.0.83 - #132
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request updates ChangesPKC JS dependency update
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized dependency upgrade with no reported transitive changes, and the build and CLI test suite pass; no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
…e KUBO_RPC_URL test startPkcDaemon resolves on the 'Communities in data path' banner, which does not mean kubo's HTTP API is listening: pkc-js rewrites kubo's Routing config and POSTs /shutdown on first connect, so the daemon restarts kubo around init. The single un-retried fetch could land in that window and fail with ECONNREFUSED on macOS CI. Every other kubo check in the suite already polls waitForKuboReady; this was the last bare one missed by the #95 fix. Closes #133
Bumps
@pkcprotocol/pkc-jsfrom 0.0.82 to 0.0.83 (latest on npm).Lockfile diff touches only pkc-js itself — no transitive dependency changes.
Also fixes a pre-existing test flake that surfaced on this branch's first CI run (macOS):
daemon uses KUBO_RPC_URL env var to configure kubo bind addressverified kubo with a single un-retriedfetchthat can land in the window where pkc-js has restarted kubo around init. Now pollswaitForKuboReady, like every other kubo check in the suite. Not caused by the version bump.Closes #133
Verification
npm run build && npm run build:test— cleannpm run test:cli— 43 files, 341 passed, 1 skipped, 0 failed