feat: bump version to 4.1.7 across all files

Updated version from 4.1.6 to 4.1.7 in:
- VERSION file
- package.json
- pyproject.toml
- All documentation files (README.md, CLAUDE.md, PLANNING.md, etc.)
- Internationalized READMEs (ja, zh, kr)
- Command documentation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
mithun50
2025-11-12 17:37:27 +01:00
parent ad80f57f63
commit a3541f43c5
13 changed files with 27 additions and 27 deletions

View File

@@ -153,12 +153,12 @@ cat test_output.txt
### **Pitfall 4: Version Inconsistency**
**Problem**: VERSION file says 4.1.6, but package.json says 4.1.5, pyproject.toml says 0.4.0.
**Problem**: VERSION file says 4.1.7, but package.json says 4.1.5, pyproject.toml says 0.4.0.
**Solution**: Understand versioning strategy:
- **Framework version** (VERSION file): User-facing version (4.1.6)
- **Framework version** (VERSION file): User-facing version (4.1.7)
- **Python package** (pyproject.toml): Library semantic version (0.4.0)
- **NPM package** (package.json): Should match framework version (4.1.6)
- **NPM package** (package.json): Should match framework version (4.1.7)
**When updating versions**:
1. Update VERSION file first
@@ -523,7 +523,7 @@ Based on real usage data:
### **Lesson 1: Documentation Drift is Real**
**What happened**: README described v2.0 plugin system that didn't exist in v4.1.6
**What happened**: README described v2.0 plugin system that didn't exist in v4.1.7
**Impact**: Users spent hours trying to install non-existent features