claude-flow 2.7.28 → 2.7.29

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -5,6 +5,99 @@ All notable changes to this project will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [2.7.29] - 2025-11-06
9
+
10
+ > **🔴 CRITICAL FIX**: Removed non-existent dependencies blocking installation
11
+
12
+ ### Summary
13
+ Fixed critical installation blocker by removing `@xenova/transformers@^3.2.0` and `onnxruntime-node` from optionalDependencies. Version 3.2.0 of transformers doesn't exist (latest is 2.17.2), causing npm install failures for all users on v2.7.24-v2.7.28.
14
+
15
+ ### 🐛 Bug Fixed
16
+
17
+ **Issue**: Users unable to install claude-flow due to non-existent dependency
18
+ ```
19
+ npm error Could not resolve dependency:
20
+ npm error optional @xenova/transformers@"^3.2.0"
21
+ ```
22
+
23
+ **Root Cause**: `package.json` specified `@xenova/transformers@^3.2.0`, but only version 2.17.2 exists on npm.
24
+
25
+ ### 🔧 Changes Made
26
+
27
+ **Removed Dependencies** (`package.json`):
28
+ ```diff
29
+ "optionalDependencies": {
30
+ "@types/better-sqlite3": "^7.6.13",
31
+ - "@xenova/transformers": "^3.2.0", // ❌ Version doesn't exist
32
+ "agentdb": "^1.3.9",
33
+ "better-sqlite3": "^12.2.0",
34
+ "diskusage": "^1.1.3",
35
+ - "node-pty": "^1.0.0",
36
+ - "onnxruntime-node": "^1.23.0" // ❌ Also removed
37
+ + "node-pty": "^1.0.0"
38
+ }
39
+ ```
40
+
41
+ ### ✅ Impact
42
+
43
+ **Before v2.7.29** (Broken):
44
+ - ❌ v2.7.24-v2.7.28: Installation fails
45
+ - Users forced to use v2.0.0-alpha.2 or pre-v2.7.24
46
+
47
+ **After v2.7.29** (Fixed):
48
+ - ✅ npm install works correctly
49
+ - ✅ All features functional
50
+ - ✅ No code changes needed (deps were optional)
51
+
52
+ ### 📋 Testing
53
+
54
+ **Docker Validation** (`tests/docker/Dockerfile.v2.7.29-test`):
55
+ ```bash
56
+ # Build and test
57
+ docker build -f tests/docker/Dockerfile.v2.7.29-test -t claude-flow-v2.7.29-test .
58
+ docker run --rm claude-flow-v2.7.29-test
59
+
60
+ ✅ Test 1: Version is v2.7.29
61
+ ✅ Test 2: @xenova/transformers removed
62
+ ✅ Test 3: onnxruntime-node removed
63
+ ✅ Test 4: Dependencies installed (726 modules)
64
+ ✅ Test 5: CLI executes successfully
65
+ ✅ Test 6: Removed deps not in node_modules
66
+ ```
67
+
68
+ ### 🚀 Installation
69
+
70
+ ```bash
71
+ # NPX users (recommended)
72
+ npx claude-flow@latest init
73
+
74
+ # Global installation
75
+ npm install -g claude-flow@latest
76
+
77
+ # Verify
78
+ claude-flow --version # v2.7.29
79
+ ```
80
+
81
+ ### 📝 Affected Versions
82
+
83
+ **Broken** (DO NOT USE):
84
+ - v2.7.24 - v2.7.28
85
+
86
+ **Fixed**:
87
+ - v2.7.29 (this release)
88
+ - v2.0.0-alpha.2 (older, still works)
89
+
90
+ ### 🔗 Related Issues
91
+
92
+ - **Fixes #858**: Critical: Invalid @xenova/transformers dependency blocks installation
93
+ - **Related to v2.7.24**: commit `aef451661` introduced the bug
94
+
95
+ ### 💡 Why This Happened
96
+
97
+ The transformers dependency was added in v2.7.24 for local semantic search but used a non-existent version number (`3.2.0` instead of `2.17.2`). Since it was in `optionalDependencies`, npm still tried to resolve it, causing installation to fail.
98
+
99
+ ---
100
+
8
101
  ## [2.7.28] - 2025-11-06
9
102
 
10
103
  > **🎯 Enhancement Release**: Removed automatic installation of agentic-payments MCP server - payment integrations now opt-in
package/bin/claude-flow CHANGED
@@ -2,7 +2,7 @@
2
2
  # Claude-Flow Smart Dispatcher - Detects and uses the best available runtime
3
3
  # Enhanced with NPX cache error handling and retry logic
4
4
 
5
- VERSION="2.7.28"
5
+ VERSION="2.7.29"
6
6
 
7
7
  # Determine the correct path based on how the script is invoked
8
8
  if [ -L "$0" ]; then
@@ -85,4 +85,9 @@ export class HelpFormatter {
85
85
  }
86
86
  }
87
87
 
88
+ //# sourceMappingURL=help-formatter.js.map/\s+/g, ' ');
89
+ return text;
90
+ }
91
+ }
92
+
88
93
  //# sourceMappingURL=help-formatter.js.map
@@ -2973,4 +2973,108 @@ if (import.meta.url === `file://${process.argv[1]}`) {
2973
2973
  await main();
2974
2974
  }
2975
2975
 
2976
+ //# sourceMappingURL=simple-cli.js.map sparc run spec-pseudocode "User profile management feature"
2977
+
2978
+ # 2. Design architecture
2979
+ npx claude-flow sparc run architect "Profile service architecture with data validation"
2980
+
2981
+ # 3. Implement with TDD
2982
+ npx claude-flow sparc tdd "user profile CRUD operations"
2983
+
2984
+ # 4. Security review
2985
+ npx claude-flow sparc run security-review "profile data access and validation"
2986
+
2987
+ # 5. Integration testing
2988
+ npx claude-flow sparc run integration "profile service with authentication system"
2989
+
2990
+ # 6. Documentation
2991
+ npx claude-flow sparc run docs-writer "profile service API documentation"
2992
+ \`\`\`
2993
+
2994
+ ### Bug Fix Workflow
2995
+ \`\`\`bash
2996
+ # 1. Debug and analyze
2997
+ npx claude-flow sparc run debug "authentication token expiration issue"
2998
+
2999
+ # 2. Write regression tests
3000
+ npx claude-flow sparc run tdd "token refresh mechanism tests"
3001
+
3002
+ # 3. Implement fix
3003
+ npx claude-flow sparc run code "fix token refresh in authentication service"
3004
+
3005
+ # 4. Security review
3006
+ npx claude-flow sparc run security-review "token handling security implications"
3007
+ \`\`\`
3008
+
3009
+ ## Configuration Files
3010
+
3011
+ ### SPARC Configuration
3012
+ - **\`.roomodes\`**: SPARC mode definitions and configurations
3013
+ - **\`.roo/\`**: Templates, workflows, and mode-specific rules
3014
+
3015
+ ### Claude-Flow Configuration
3016
+ - **\`memory/\`**: Persistent memory and session data
3017
+ - **\`coordination/\`**: Multi-agent coordination settings
3018
+
3019
+ ## Git Workflow Integration
3020
+
3021
+ ### Commit Strategy with SPARC
3022
+ - **Specification commits**: After completing requirements analysis
3023
+ - **Architecture commits**: After design phase completion
3024
+ - **TDD commits**: After each Red-Green-Refactor cycle
3025
+ - **Integration commits**: After successful component integration
3026
+ - **Documentation commits**: After completing documentation updates
3027
+
3028
+ ### Branch Strategy
3029
+ - **\`feature/sparc-<feature-name>\`**: Feature development with SPARC methodology
3030
+ - **\`hotfix/sparc-<issue>\`**: Bug fixes using SPARC debugging workflow
3031
+ - **\`refactor/sparc-<component>\`**: Refactoring using optimization mode
3032
+
3033
+ ## Troubleshooting
3034
+
3035
+ ### Common SPARC Issues
3036
+ - **Mode not found**: Check \`.roomodes\` file exists and is valid JSON
3037
+ - **Memory persistence**: Ensure \`memory/\` directory has write permissions
3038
+ - **Tool access**: Verify required tools are available for the selected mode
3039
+ - **Namespace conflicts**: Use unique memory namespaces for different features
3040
+
3041
+ ### Debug Commands
3042
+ \`\`\`bash
3043
+ # Check SPARC configuration
3044
+ npx claude-flow sparc modes
3045
+
3046
+ # Verify memory system
3047
+ npx claude-flow memory stats
3048
+
3049
+ # Check system status
3050
+ npx claude-flow status
3051
+
3052
+ # View detailed mode information
3053
+ npx claude-flow sparc info <mode-name>
3054
+ \`\`\`
3055
+
3056
+ ## Project Architecture
3057
+
3058
+ This SPARC-enabled project follows a systematic development approach:
3059
+ - **Clear separation of concerns** through modular design
3060
+ - **Test-driven development** ensuring reliability and maintainability
3061
+ - **Iterative refinement** for continuous improvement
3062
+ - **Comprehensive documentation** for team collaboration
3063
+ - **AI-assisted development** through specialized SPARC modes
3064
+
3065
+ ## Important Notes
3066
+
3067
+ - Always run tests before committing (\`npm run test\`)
3068
+ - Use SPARC memory system to maintain context across sessions
3069
+ - Follow the Red-Green-Refactor cycle during TDD phases
3070
+ - Document architectural decisions in memory for future reference
3071
+ - Regular security reviews for any authentication or data handling code
3072
+
3073
+ For more information about SPARC methodology, see: https://github.com/ruvnet/claude-code-flow/docs/sparc.md
3074
+ `;
3075
+ }
3076
+ if (isMainModule(import.meta.url)) {
3077
+ await main();
3078
+ }
3079
+
2976
3080
  //# sourceMappingURL=simple-cli.js.map