chore(deps): upgrade @pkcprotocol/pkc-js 0.0.62 -> 0.0.69#115
Conversation
pkc-js 0.0.69 bumps remeda 1.57.0 -> 2.39.0; remeda v2 removed keys.strict() (keys() is strict by default), so adapt the one call site in community edit.
|
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 (2)
📝 WalkthroughWalkthroughThe PR upgrades ChangesPKC dependency update
Community edit behavior
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 src/cli/commands/community/edit.tsOops! 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 |
Upgrades @pkcprotocol/pkc-js from 0.0.62 to 0.0.69 (issue #114).
Changes
@pkcprotocol/pkc-js0.0.62 -> 0.0.69 (exact version).src/cli/commands/community/edit.ts: the upgrade bumps pkc-js's remeda dependency 1.57.0 -> 2.39.0, and remeda v2 removedkeys.strict()(keys()is strict by default). Adapted the one affected call site; all other remeda usage (omit,pick,isPlainObject) is unchanged in v2.Verification
npm run build && npm run build:testpasses.npm run test:cli: 310 passed, 1 skipped (40 test files), no failures.Note: this repo imports
remedadirectly in several files but does not declare it inpackage.json— it resolves via hoisting from pkc-js. Worth declaring it as a direct dependency in a follow-up to avoid future silent major bumps.Summary by CodeRabbit