chore(deps): upgrade @pkcprotocol/pkc-js 0.0.81 -> 0.0.82

[Rinse12]

Closes #126

What

Bumps @pkcprotocol/pkc-js from 0.0.81 to 0.0.82 (latest). Dependency-only change — no source edits.

Upstream changes

v0.0.82

Features

• crosspost: embed the reposted comment in comment.crosspost (feat(crosspost): embed the reposted comment in comment.crosspost (#32) pkcprotocol/pkc-js#248, closes implement crosspost pkcprotocol/pkc-js#32) — a crossposting comment now carries the full CommentIpfs of the comment it reposts, so the crossposting community's mods can moderate it in place. Adds a noCrossposts community feature.

Bug Fixes

• pkc: stop in-flight publications in destroy() and drain their background community refresh (fix(pkc): stop in-flight publications in destroy() and drain their background community refresh pkcprotocol/pkc-js#271, closes fix(pkc): stop in-flight publications in pkc.destroy() pkcprotocol/pkc-js#270)

Neither needs CLI plumbing here: community features are passed through generically rather than enumerated in src/, so noCrossposts is reachable without changes.

Verification

• npm run build && npm run build:test — clean
• npm run test:cli — 43 files, 333 passed, 6 skipped

One file (test/cli/daemon.test.ts) hit a pre-existing flake on the first full run; it passes on re-run (23/23) and is unrelated to this bump. Details below.

Follow-up worth a look (not changed here)

test/helpers/daemon-helpers.ts retries the TOCTOU port race via isAddressInUseError, which matches three signatures:

/address already in use|EADDRINUSE|became occupied before the daemon could bind it/i

There is a fourth wording it does not cover. src/ipfs/startIpfs.ts:215 raises the CLI's own pre-bind guard as:

Cannot start IPFS daemon because the IPFS Gateway port 0.0.0.0:37685 (configured as /ip4/0.0.0.0/tcp/37685) is already in use.

That string contains is already in use but not address already in use, so the matcher returns false, startPkcDaemonWithDynamicPorts rethrows instead of retrying with a fresh port set, and the suite's beforeAll dies. Same root cause as issues #87 / #97, just a third message wording — the gateway port, where the earlier fixes covered the raw bind failure and the PKC RPC pre-bind guard.

A second, avoidable failure lands on top: afterAll still runs and calls waitForPortFree(rpcPort, ...) with rpcPort never assigned, so alongside the real startup error the run also reports

TypeError: The "options" or "port" or "path" argument must be specified
  at test/helpers/daemon-helpers.ts:198  // socket.connect(port, host)

which points at the teardown rather than the lost bind race. Both errors are reported, so the cause is not hidden outright, but the spurious one is the eye-catching part.

Tracked and fixed separately in #128 — this PR stays dependency-only.

[coderabbitai]

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: c46c1c78-2c64-4e75-b822-4ee9a6aeea7f

📥 Commits

Reviewing files that changed from the base of the PR and between bbc0d40 and a6e1794.

⛔ 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 PR updates the @pkcprotocol/pkc-js dependency in package.json from version 0.0.81 to 0.0.82.

Changes

PKC dependency update

Layer / File(s)	Summary
Update dependency version package.json	The manifest changes @pkcprotocol/pkc-js from 0.0.81 to 0.0.82.

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

Merge Risk: ⚪ Minimal · up to a6e17

This dependency-only upgrade has passed the reported build and CLI checks, and no actionable merge-blocking risk remains beyond normal review and verification.

Possibly related issues

• chore(deps): upgrade @pkcprotocol/pkc-js 0.0.81 -> 0.0.82 #126: This issue describes the same @pkcprotocol/pkc-js update from 0.0.81 to 0.0.82.

Possibly related PRs

• bitsocialnet/bitsocial-cli#123: This PR updates the same dependency and continues the version upgrade to 0.0.82.
• bitsocialnet/bitsocial-cli#115: This PR directly updates the same dependency to an earlier version.
• bitsocialnet/bitsocial-cli#86: This PR updates the same dependency and includes related API and test changes.

🚥 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 identifies the dependency upgrade from version 0.0.81 to 0.0.82.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/upgrade-pkc-js-0.0.82

---

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