You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Bump version to 6.4.1
- Update CHANGELOG.md with release notes
- Update README.md with new version
- Update version references
Release: v6.4.1
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,23 @@
44
44
45
45
## 🆕 Recent Updates
46
46
47
+
### v6.4.1 (November 2025)
48
+
49
+
**Windows Compatibility Fix**
50
+
51
+
-**Bash Fallback**: spec-cli.py now automatically falls back to bash scripts when PowerShell equivalents don't exist
52
+
- Enables Windows users to run workflow commands via Git Bash/WSL without errors
53
+
- Graceful fallback with informative message: "Note: PowerShell script not found, using bash"
54
+
- Fixes "PowerShell script not found" error for feature-workflow and other commands
55
+
-**Git Permissions**: Fixed executable permissions for ship-prod-workflow.sh (100755 mode)
56
+
-**Python Cache**: Added __pycache__ to .gitignore to prevent accidental commits
57
+
58
+
**Problem Solved**: Windows users couldn't run workflow commands because spec-cli.py expected PowerShell scripts that were never created during the CLI migration. Only bash scripts exist, but there was no fallback mechanism.
59
+
60
+
**Impact**: Windows users with Git Bash/WSL can now run all workflow commands seamlessly. Cross-platform compatibility restored without requiring PowerShell script duplication.
0 commit comments