fix: use direct JSON edit instead of npm version to avoid 'Version not changed' error

- Replace npm version command with direct package.json manipulation
- Prevents error when version already matches tag
- More robust and reliable approach

Author: Test User

.github/workflows/release.yml

@@ -78,13 +78,15 @@ jobs:
 
       - name: Update package.json version
         run: |
-          CURRENT_VERSION=$(node -p "require('./package.json').version")
           TAG_VERSION="${{ steps.get_version.outputs.version }}"
+          CURRENT_VERSION=$(node -p "require('./package.json').version")
+          echo "Current version: $CURRENT_VERSION"
+          echo "Tag version: $TAG_VERSION"
           if [ "$CURRENT_VERSION" != "$TAG_VERSION" ]; then
             echo "Updating version from $CURRENT_VERSION to $TAG_VERSION"
-            npm version $TAG_VERSION --no-git-tag-version
+            node -e "const fs = require('fs'); const pkg = JSON.parse(fs.readFileSync('package.json')); pkg.version = '$TAG_VERSION'; fs.writeFileSync('package.json', JSON.stringify(pkg, null, 2) + '\n');"
           else
-            echo "Version already matches tag: $CURRENT_VERSION"
+            echo "Version already matches tag: $CURRENT_VERSION - skipping update"
           fi
 
       - name: Verify package.json