test: trigger RC numbering validation

� New GitHub Actions RC numbering system:
- Should create v0.5.0-rc.9 (next sequential RC based on existing git tags)
- New logic looks at existing tags instead of run_number for proper sequencing
- Validates smart RC increment for future v0.6.0-rc.1 starting fresh

Minor change: Added comment to extension.ts to trigger build

Author: Wilson421

.github/workflows/release.yml

@@ -8,11 +8,10 @@ on:
     branches:
       - "release/**"
       - main
+
     paths-ignore:
       - "**.md"
       - "docs/**"
-      - ".github/**"
-
   # Manual workflow dispatch for emergency releases
   workflow_dispatch:
     inputs:
@@ -54,7 +53,18 @@ jobs:
             VERSION="${BASH_REMATCH[1]}"
             echo "version=$VERSION" >> $GITHUB_OUTPUT
           elif [[ "${{ github.ref }}" =~ ^refs/heads/release/v(.*)$ ]]; then
-            VERSION="${BASH_REMATCH[1]}-rc.${{ github.run_number }}"
+            BASE_VERSION="${BASH_REMATCH[1]}"
+            
+            # Find the highest existing RC for this version
+            EXISTING_RCS=$(git tag -l "v${BASE_VERSION}-rc.*" | sed "s/v${BASE_VERSION}-rc\.//" | sort -n | tail -1)
+            
+            if [[ -z "$EXISTING_RCS" ]]; then
+              RC_NUMBER=1
+            else
+              RC_NUMBER=$((EXISTING_RCS + 1))
+            fi
+            
+            VERSION="${BASE_VERSION}-rc.${RC_NUMBER}"
             echo "version=$VERSION" >> $GITHUB_OUTPUT
           else
             PACKAGE_VERSION=$(node -p "require('./package.json').version")

docs/CONTRIBUTING.md

@@ -359,36 +359,52 @@ gh pr list
 | `npm run test`         | Run test suite via `vscode-test`                |
 | `npm run watch`        | Watch build and test                            |
 | `npm run check-types`  | TypeScript compile check (no emit)              |
-| `npm run bump-version` | Smart semantic version bumping from git commits |
+| `npm run bump-version` | **EWC3 Custom:** Analyze git commits and suggest semantic version |
+| `npm version patch/minor/major` | **NPM Native:** Immediate version bump + git commit + git tag |
 
 <details>
 <summary><strong>🔢 Smart Version Management</strong> (click to expand)</summary>
 
-**Automatic Version Bumping:**
+**Automatic Version Analysis (EWC3 Labs Custom):**
 ```bash
-# Analyze commits and bump version automatically
+# Our smart script analyzes commit messages and suggests versions
 npm run bump-version
 
-# The script analyzes your git history for:
+# Analyzes your git history for conventional commit patterns:
 # - feat: → minor version bump (0.5.0 → 0.6.0)
 # - fix: → patch version bump (0.5.0 → 0.5.1) 
 # - BREAKING: → major version bump (0.5.0 → 1.0.0)
+
+# Manual override (updates package.json only, no git operations)
+npm run bump-version 0.6.0
 ```
 
-**Manual Version Control:**
+**When to Use Which:**
+
+- **`npm version`** - When you want to **immediately release** with git commit + tag
+- **`npm run bump-version`** - When you want to **preview/analyze** what the next version should be
+- **GitHub Actions** - Uses our script for **automated releases** from branch pushes
+
+**Manual Version Control (Native NPM):**
 ```bash
-# Bump specific version types
-npm version patch   # 0.5.0 → 0.5.1
-npm version minor   # 0.5.0 → 0.6.0  
-npm version major   # 0.5.0 → 1.0.0
+# Native NPM versioning commands (standard industry practice)
+npm version patch   # 0.5.0 → 0.5.1 + git commit + git tag
+npm version minor   # 0.5.0 → 0.6.0 + git commit + git tag  
+npm version major   # 0.5.0 → 1.0.0 + git commit + git tag
+
+# Pre-release versions  
+npm version prerelease  # 0.5.0 → 0.5.1-0 + git commit + git tag
+npm version prepatch    # 0.5.0 → 0.5.1-0 + git commit + git tag
+npm version preminor    # 0.5.0 → 0.6.0-0 + git commit + git tag
 
-# Pre-release versions
-npm version prerelease  # 0.5.0 → 0.5.1-0
-npm version prepatch    # 0.5.0 → 0.5.1-0
-npm version preminor    # 0.5.0 → 0.6.0-0
+# Dry run (see what would happen without doing it)
+npm version patch --dry-run
 ```
 
-> 🧠 **Smart Tip:** The release pipeline automatically handles version bumping, but you can use `npm run bump-version` locally to preview what version would be generated.
+> 🧠 **Smart Tip:** 
+> - **For preview:** Use `npm run bump-version` to see what version our script suggests
+> - **For immediate release:** Use `npm version patch/minor/major` to bump + commit + tag in one step  
+> - **For automation:** GitHub Actions uses our custom script for branch-based releases
 
 </details>
 

docs/PUBLISHING_GUIDE.md

@@ -2,6 +2,41 @@
 
 This guide covers the complete process for publishing the Excel Power Query Editor extension to the VS Code Marketplace using **GitHub Actions automation**.
 
+## 🔢 Understanding Version Management
+
+### NPM Native vs EWC3 Custom Versioning
+
+**`npm version` (NPM Built-in Command):**
+- **Industry Standard**: Built into NPM, used by millions of projects
+- **All-in-One**: Updates package.json + creates git commit + creates git tag  
+- **Immediate Action**: Perfect for traditional "commit and tag" release workflow
+- **Examples**:
+  ```bash
+  npm version patch   # 0.5.0 → 0.5.1 + commit + tag
+  npm version minor   # 0.5.0 → 0.6.0 + commit + tag
+  npm version major   # 0.5.0 → 1.0.0 + commit + tag
+  ```
+
+**`npm run bump-version` (EWC3 Labs Custom Script):**
+- **Smart Analysis**: Reads your git commit messages and suggests semantic versions
+- **Preview Mode**: Shows what version should be next without making changes
+- **Package.json Only**: Updates version but doesn't create commits/tags (leaves git operations to you)
+- **Conventional Commits**: Analyzes `feat:`, `fix:`, `BREAKING:` patterns
+- **Examples**:
+  ```bash
+  npm run bump-version           # Analyzes commits → suggests version → updates package.json
+  npm run bump-version 0.6.0     # Force sets version in package.json (no git operations)
+  ```
+
+### When to Use Which Approach:
+
+| Scenario | Recommended Tool | Why |
+|----------|------------------|-----|
+| **Quick Release** | `npm version patch` | One command does everything: version + commit + tag |
+| **Preview Next Version** | `npm run bump-version` | See what our script thinks the version should be |
+| **Automated CI/CD** | GitHub Actions uses our script | Branch-based releases with smart versioning |
+| **Manual Override** | `npm run bump-version 0.6.0` | Set specific version without git operations |
+
 ## 🚀 Automated Publishing (Recommended)
 
 The project includes a comprehensive GitHub Actions workflow that automates the entire release process. Here's how to set it up and use it:
@@ -134,20 +169,33 @@ vsce login ewc3labs
 # Enter your Personal Access Token when prompted
 ```
 
-### Manual Publishing Steps:
+### Manual Publishing Steps (Traditional Approach):
 
 ```bash
-# 1. Update version
-npm version 0.5.0 --no-git-tag-version
+# Option A: Use NPM native versioning (creates git commit + tag)
+npm version 0.5.0        # Updates package.json + commits + tags
+npm test                 # Ensure everything works
+npm run compile          # Build extension
+vsce package            # Create VSIX
+vsce publish            # Publish to marketplace
+
+# Option B: Manual version update (no git operations)
+npm run bump-version 0.5.0  # Update package.json only (EWC3 script)
+# OR: Edit package.json manually
+npm test && npm run compile
+vsce package && vsce publish
+git add . && git commit -m "chore: release v0.5.0"
+git tag v0.5.0 && git push --tags
+```
 
-# 2. Test build
-npm test
-npm run compile
-vsce package
+### Version Management Options:
 
-# 3. Publish
-vsce publish
-```
+| Method | What It Does | When To Use |
+|--------|-------------|-------------|
+| `npm version 0.5.0` | Updates package.json + git commit + git tag | **Traditional release workflow** |
+| `npm run bump-version` | Analyzes commits, suggests version, updates package.json only | **Preview what version should be next** |
+| `npm run bump-version 0.5.0` | Sets specific version in package.json only | **Manual override without git operations** |
+| GitHub Actions | Uses our script for automated versioning from branch names | **Automated CI/CD releases** |
 
 ## 📋 Pre-Release Checklist
 

src/extension.ts

@@ -12,12 +12,12 @@ function isTestEnvironment(): boolean {
 	       typeof global.describe !== 'undefined'; // Jest/Mocha detection
 }
 
-// Helper to get test fixture path
+// Helper to get test fixture path  
 function getTestFixturePath(filename: string): string {
 	return path.join(__dirname, '..', 'test', 'fixtures', filename);
 }
 
-// File watchers storage
+// File watchers storage 
 const fileWatchers = new Map<string, { chokidar: FSWatcher; vscode: vscode.FileSystemWatcher | null; document: vscode.Disposable | null }>();
 const recentExtractions = new Set<string>(); // Track recently extracted files to prevent immediate auto-sync
 
@@ -161,7 +161,7 @@ function cleanupOldBackups(excelFile: string): void {
 	}
 }
 
-// Enhanced logging function with context and log levels
+// Enhanced logging function with context and log levels, smart emoji or text 'level' support, and respects user log level settings
 function log(message: string, context: string = '', level: string = 'info'): void {
 	const config = getConfig();
 	const userLogLevel = (config.get<string>('logLevel', 'info') || 'info').toLowerCase();