chore(deps): upgrade @pkcprotocol/pkc-js 0.0.77 -> 0.0.81 - #123
Conversation
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)
|
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)
📝 WalkthroughWalkthroughThe PR updates ChangesDependency upgrade
Estimated code review effort: 1 (Trivial) | ~2 minutes Mergeability Score: ⚪ Minimal · up to 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)
✨ Finishing Touches🧪 Generate unit tests (beta)
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
package.jsonOops! Something went wrong! :( ESLint: 8.27.0 Error: ESLint configuration in --config » eslint-config-oclif is invalid:
Referenced from: /.eslintrc 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 |
Closes #122
What
Bumps
@pkcprotocol/pkc-jsfrom0.0.77to0.0.81(latest). Dependency-only change — no source edits.Upstream changes
v0.0.78 — no user-facing changes.
v0.0.79
peer:updatelistener when the provider stream throws (fix(helia): detach peer:update listener when the provider stream throws pkcprotocol/pkc-js#256)v0.0.80
nameResolved(feat(community): delegated records advertise their anchor; claim-first nameResolved pkcprotocol/pkc-js#260)v0.0.81
block.putcall so a repo gc cannot delete itVerification
npm run build && npm run build:test— cleannpm run test:cli— 41 files, 319 passed, 1 skippedFollow-up worth a look (not changed here)
pkc-js 0.0.79 added its own repo GC schedule in
local-community/cleanup.js:cleanUpIpfsRepoIfDueruns 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 insrc/cli/commands/daemon.ts:744) in 6757a87, which drives an independent hourlyrepo/gcover 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