Skip to content

chore(deps): upgrade @pkcprotocol/pkc-js 0.0.82 -> 0.0.83 - #132

Merged
Rinse12 merged 2 commits into
masterfrom
chore/upgrade-pkc-js-0.0.83
Aug 17, 2026
Merged

chore(deps): upgrade @pkcprotocol/pkc-js 0.0.82 -> 0.0.83#132
Rinse12 merged 2 commits into
masterfrom
chore/upgrade-pkc-js-0.0.83

Conversation

@Rinse12

@Rinse12 Rinse12 commented Aug 17, 2026

Copy link
Copy Markdown
Member

Bumps @pkcprotocol/pkc-js from 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 address verified kubo with a single un-retried fetch that can land in the window where pkc-js has restarted kubo around init. Now polls waitForKuboReady, like every other kubo check in the suite. Not caused by the version bump.

Closes #133

Verification

  • npm run build && npm run build:test — clean
  • npm run test:cli — 43 files, 341 passed, 1 skipped, 0 failed

@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: af30f8f6-21ed-4a7c-ac7b-e68098e78e18

📥 Commits

Reviewing files that changed from the base of the PR and between 75303e0 and c5d59ad.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The pull request updates @pkcprotocol/pkc-js from version 0.0.82 to version 0.0.83 in package.json.

Changes

PKC JS dependency update

Layer / File(s) Summary
Update PKC JS dependency version
package.json
The dependency declaration changes from 0.0.82 to 0.0.83.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to c5d59

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)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the dependency upgrade from @pkcprotocol/pkc-js 0.0.82 to 0.0.83.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/upgrade-pkc-js-0.0.83

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.

…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
@Rinse12
Rinse12 merged commit c4ca253 into master Aug 17, 2026
4 checks passed
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.

Flaky daemon test: KUBO_RPC_URL test still uses a one-shot fetch that races the pkc-js kubo restart (lineage #95)

1 participant