chore(deps): upgrade kubo 0.41.0 → 0.42.0#81
Conversation
Reviewed the kubo v0.42.0 changelog against bitsocial-cli's usage (ipfs init / config profile apply server / repo migrate / daemon --enable-namesys-pubsub --migrate, plus Addresses/AutoTLS/Gateway config edits in src/ipfs/startIpfs.ts). No breaking changes affect us: - Provide.DHT.Interval=0 semantics change (the only breaking change) does not apply: we never set Provide.* in our config merge. - --enable-namesys-pubsub and --migrate remain valid, not deprecated. - ipfs repo migrate still works (now retries across gateways). Verified: build + build:test pass; full test:cli passes (259 passed, 1 skipped) driving the real kubo 0.42.0 binary.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughKubo npm package dependency is upgraded from ChangesKubo dependency upgrade
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Upgrades the bundled
kubodependency from0.41.0to0.42.0(latest official release from the ipfs/npm-kubo GitHub Actions pipeline; maps to kubo binary v0.42.0).Fixes #80.
Changelog review vs. our usage
Reviewed the v0.42.0 release notes against how bitsocial-cli drives kubo in
src/ipfs/startIpfs.ts:ipfs init,ipfs config profile apply server,ipfs repo migrate,ipfs daemon --enable-namesys-pubsub --migrate, plus config edits toAddresses,AutoTLS.Enabled, andGateway.PublicGateways.No breaking changes affect us:
Provide.DHT.Interval=0semantics change — the only breaking change in 0.42.0; daemon now refuses startup ifProvide.DHT.Interval=0is set without explicitProvide.Enabled. We never setProvide.*in our config merge and don't depend on theserverprofile touching it. Not applicable.--enable-namesys-pubsub/--migrate— still valid in 0.42.0, not deprecated or removed.ipfs repo migrate— still works; now more resilient (retries across gateways with HTTP timeouts).ipfs routing providedeprecated (→ipfs provide once) — we don't use it.Internal.ShutdownTimeoutdefault 12h,Migration.DownloadSources,Provide.DHT.SendProviderRecordTimeout) and new RPC subcommands don't affect existing usage.Avoided npm
kubo@1.0.1— hand-published by an individual rather than the official GitHub Actions pipeline; kubo binary releases follow0.x.0.Verification
npm run build && npm run build:test✅npm run test:cli✅ — 259 passed, 1 skipped (32 files), including the daemon and kubo restart-race suites that drive the real kubo binary, confirmedipfs version 0.42.0.Summary by CodeRabbit