Skip to content

chore(deps): upgrade @pkcprotocol/pkc-js 0.0.77 -> 0.0.81 - #123

Merged
Rinse12 merged 1 commit into
masterfrom
chore/upgrade-pkc-js-0.0.81
Aug 13, 2026
Merged

chore(deps): upgrade @pkcprotocol/pkc-js 0.0.77 -> 0.0.81#123
Rinse12 merged 1 commit into
masterfrom
chore/upgrade-pkc-js-0.0.81

Conversation

@Rinse12

@Rinse12 Rinse12 commented Aug 13, 2026

Copy link
Copy Markdown
Member

Closes #122

What

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

Upstream changes

v0.0.78 — no user-facing changes.

v0.0.79

v0.0.80

v0.0.81

Verification

  • npm run build && npm run build:test — clean
  • npm run test:cli — 41 files, 319 passed, 1 skipped

Follow-up worth a look (not changed here)

pkc-js 0.0.79 added its own repo GC schedule in local-community/cleanup.js: cleanUpIpfsRepoIfDue runs at the end of every community sync with a 1-hour-per-kubo-RPC-URL floor, single-flighted by kubo URL.

This repo added startRepoGcScheduler (src/ipfs/repoGc.ts, wired in src/cli/commands/daemon.ts:744) in 6757a87, which drives an independent hourly repo/gc over the same RPC. The two schedulers don't know about each other, so on a daemon hosting communities the effective sweep rate roughly doubles and two full sweeps can overlap. pkc-js's own comment notes that since kubo 0.43.0 GC and in-flight MFS writes hold each other off, so overlapping sweeps are not free.

They are not exactly redundant, though: pkc-js only GCs as a side effect of a community sync, so a bitsocial daemon hosting zero communities (a seed-only node) would never GC if ours were removed. Deciding whether to drop, gate, or keep our scheduler is a behaviour change, so it is left out of this dependency bump — filing separately if you want it addressed.

Summary by CodeRabbit

  • Chores
    • Updated the PKC JavaScript dependency to version 0.0.81 for improved compatibility and maintenance.

Upstream fixes picked up:

- helia: detach peer:update listener when the provider stream throws (#256)
- kubo: run repo GC hourly per daemon instead of on a StorageMax
  watermark (#259)
- community: delegated records advertise their anchor; claim-first
  nameResolved (#260)
- kubo: pin the pubsub topic block in the block.put call so a repo gc
  cannot delete it
- kubo: remove the address rewriter proxy that now degrades provider
  records (#263)
@coderabbitai

coderabbitai Bot commented Aug 13, 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: 5e0eec7d-8151-48fe-b884-f63be527370b

📥 Commits

Reviewing files that changed from the base of the PR and between 88814f1 and 1cc8952.

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

📝 Walkthrough

Walkthrough

The PR updates @pkcprotocol/pkc-js from version 0.0.77 to 0.0.81 in package.json.

Changes

Dependency upgrade

Layer / File(s) Summary
Update PKC JS dependency
package.json
The declared @pkcprotocol/pkc-js version changes from 0.0.77 to 0.0.81.

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

Mergeability Score: ⚪ Minimal · up to 1cc89

This is a dependency-only upgrade with successful build and test verification; no actionable merge-blocking risk remains beyond normal checks and review.

Possibly related issues

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
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 version 0.0.77 to 0.0.81.
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/upgrade-pkc-js-0.0.81

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

package.json

Oops! Something went wrong! :(

ESLint: 8.27.0

Error: ESLint configuration in --config » eslint-config-oclif is invalid:

  • Unexpected top-level property "__esModule".

Referenced from: /.eslintrc
at ConfigValidator.validateConfigSchema (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2156:19)
at ConfigArrayFactory._normalizeConfigData (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2998:19)
at ConfigArrayFactory._loadConfigData (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2963:21)
at ConfigArrayFactory._loadExtendedShareableConfig (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3264:21)
at ConfigArrayFactory._loadExtends (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3135:25)
at ConfigArrayFactory._normalizeObjectConfigDataBody (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3074:25)
at _normalizeObjectConfigDataBody.next ()
at ConfigArrayFactory._normalizeObjectConfigData (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3019:20)
at _normalizeObjectConfigData.next ()
at ConfigArrayFactory.loadFile (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2829:16)


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.

@Rinse12
Rinse12 merged commit 53b42e5 into master Aug 13, 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.

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

1 participant