fix(cli): bump version to 0.5.1 (SMI-3537)#343
Conversation
…I-3537) @skillsmith/cli@0.5.0 was published with exact-pinned @skillsmith/core@0.4.15. Subsequent squash-merges reverted local to 0.4.3, creating a version gap. Bumping to 0.5.1 to advance past the problematic 0.5.0 publish. Co-Authored-By: claude-flow <ruv@ruv.net> Co-Authored-By: Claude <noreply@anthropic.com>
Performance Benchmark Results╔═══════════════════════════════════════════════════════════════╗ Running 50 iterations with 10 warmup... --- Memory Operations --- --- Embedding Search --- --- Recommendation Pipeline --- ═══════════════════════════════════════════════════════════════ V3 Migration Benchmark ReportDate: 2026-03-22T00:32:46.862Z Results
Summary
Notes
|
Summary
@skillsmith/clifrom0.4.3to0.5.1to resolve npm registry version regression0.5.0was published with exact-pinned@skillsmith/core@0.4.15; subsequent squash-merges reverted local to0.4.30.5.1Post-merge action
npm deprecate @skillsmith/cli@0.5.0 "Published with stale core dependency (0.4.15 exact pin). Use >=0.5.1"Test plan
npm run lint— zero errorsnpm run format:check— all formattednpm run typecheck— cleannpm test -w @skillsmith/cli— 441 tests passed🤖 Generated with claude-flow