Update config validator and includes in all docs

Author: Genevieve Nuebel

.github/config_validator.rb

@@ -75,3 +75,6 @@ def validate_semantic_versioning!
     end
   end
 end
+
+# CLI Interface - allows direct execution from GitHub Actions
+ConfigValidator.validate!(ARGV[0], ARGV[1]) if __FILE__ == $0

.github/workflows/generate.yml

@@ -28,37 +28,17 @@ jobs:
       spec_url: ${{ steps.validate.outputs.spec_url }}
     steps:
       - uses: actions/checkout@v3
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 3.1
       - name: Validate configuration
         id: validate
         run: |
           API_VERSION="${{ github.event.inputs.api_version }}"
           CONFIG_FILE="openapi/config-${API_VERSION}.yml"
-          # Versioned spec URLs (manual workflow uses 'master' branch)
-          # Note: Manual workflow doesn't need commit SHA since developer controls timing
-          # CDN cache race condition only affects automated repository_dispatch triggers
-          # v20111101 -> https://raw.githubusercontent.com/mxenabled/openapi/master/openapi/v20111101.yml
-          # v20250224 -> https://raw.githubusercontent.com/mxenabled/openapi/master/openapi/v20250224.yml
           SPEC_URL="https://raw.githubusercontent.com/mxenabled/openapi/master/openapi/${API_VERSION}.yml"
           
-          # Check config file exists
-          if [ ! -f "$CONFIG_FILE" ]; then
-            echo "❌ Config file not found: $CONFIG_FILE"
-            exit 1
-          fi
-          
-          # Validate semantic versioning (major must match API version)
-          CURRENT_VERSION=$(grep 'npmVersion' "$CONFIG_FILE" | cut -d':' -f2 | tr -d ' ')
-          MAJOR_VERSION=$(echo "$CURRENT_VERSION" | cut -d'.' -f1)
-          
-          if [ "$API_VERSION" = "v20111101" ] && [ "$MAJOR_VERSION" != "2" ]; then
-            echo "❌ Semantic versioning error: v20111101 must have major version 2, found $MAJOR_VERSION"
-            exit 1
-          fi
-          
-          if [ "$API_VERSION" = "v20250224" ] && [ "$MAJOR_VERSION" != "3" ]; then
-            echo "❌ Semantic versioning error: v20250224 must have major version 3, found $MAJOR_VERSION"
-            exit 1
-          fi
+          ruby .github/config_validator.rb "$CONFIG_FILE" "$API_VERSION"
           
           echo "✅ Validation passed"
           echo "config_file=$CONFIG_FILE" >> $GITHUB_OUTPUT

.github/workflows/generate_publish_release.yml

@@ -59,6 +59,8 @@ jobs:
       - uses: ruby/setup-ruby@v1
         with:
           ruby-version: 3.1
+      - name: Validate configuration
+        run: ruby .github/config_validator.rb "${{ matrix.config_file }}" "${{ matrix.api_version }}"
       - name: Bump version
         id: bump_version
         run: |
@@ -75,7 +77,7 @@ jobs:
           # Versioned spec URLs with commit SHA to avoid GitHub CDN cache race condition
           # Problem: GitHub's raw.githubusercontent.com CDN caches files for 5 minutes
           # If openapi repo commits and immediately triggers this workflow, CDN may serve stale spec
-          # Solution: Use commit SHA in URL to bypass cache and guarantee correct spec version
+          # Using commit SHA in URL to bypass cache and guarantee correct spec version
           # Falls back to 'master' if openapi doesn't send commit_sha
           openapi-generator-cli generate \
             -i https://raw.githubusercontent.com/mxenabled/openapi/${{ github.event.client_payload.commit_sha || 'master' }}/openapi/${{ matrix.api_version }}.yml \

docs/Adding-a-New-API-Version.md

@@ -85,28 +85,28 @@ api_version:
     - v20300101    # NEW
 ```
 
-**Location 2: Semantic versioning validation**
+**Location 2: Update ConfigValidator**
 
-In the `Validate` job's validation step, add a new conditional check for your version:
+In `.github/config_validator.rb`, add your new version to the `SUPPORTED_VERSIONS` mapping:
 
-```yaml
-if [ "$API_VERSION" = "v20111101" ] && [ "$MAJOR_VERSION" != "2" ]; then
-  echo "❌ Semantic versioning error: v20111101 must have major version 2, found $MAJOR_VERSION"
-  exit 1
-fi
-
-if [ "$API_VERSION" = "v20250224" ] && [ "$MAJOR_VERSION" != "3" ]; then
-  echo "❌ Semantic versioning error: v20250224 must have major version 3, found $MAJOR_VERSION"
-  exit 1
-fi
-
-if [ "$API_VERSION" = "v20300101" ] && [ "$MAJOR_VERSION" != "4" ]; then
-  echo "❌ Semantic versioning error: v20300101 must have major version 4, found $MAJOR_VERSION"
-  exit 1
-fi
+```ruby
+class ConfigValidator
+  SUPPORTED_VERSIONS = {
+    "v20111101" => 2,  # Major version must be 2
+    "v20250224" => 3,  # Major version must be 3
+    "v20300101" => 4   # Major version must be 4 (NEW)
+  }.freeze
+  # ... rest of class unchanged
+end
 ```
 
-This ensures the major version in your config file matches the expected value for that API version.
+The `ConfigValidator` automatically validates that:
+- The API version is in `SUPPORTED_VERSIONS`
+- The major version in your config file matches the expected value (e.g., v20300101 → major version 4)
+- The config file syntax is valid YAML
+- The file exists at the specified path
+
+**No workflow changes needed** — the existing validation step in `generate.yml` calls `ConfigValidator` with your new version, and it automatically validates using the updated mapping.
 
 ### 2.2 Update generate_publish_release.yml
 
@@ -363,7 +363,7 @@ Use this checklist to verify you've completed all steps:
 - [ ] Created `openapi/config-v20300101.yml` with correct syntax
 - [ ] Major version in config is unique and sequential (4.0.0 for v20300101)
 - [ ] Updated `.github/workflows/generate.yml` with new version in dropdown options
-- [ ] Updated `.github/workflows/generate.yml` with semantic versioning validation
+- [ ] Updated `.github/config_validator.rb` with new version in `SUPPORTED_VERSIONS` mapping
 - [ ] Updated `.github/workflows/generate_publish_release.yml` with version-to-config mapping in Setup job
 - [ ] Updated `.github/changelog_manager.rb` with new version in `API_VERSION_ORDER` array
 - [ ] Updated `.github/workflows/on-push-master.yml` path triggers with `v20300101/**`
@@ -397,16 +397,16 @@ Use this checklist to verify you've completed all steps:
 **Solution**: Verify the version is listed in the `on.workflow_dispatch.inputs.api_version.options` section and YAML syntax is valid
 
 ### Semantic versioning validation fails
-**Cause**: Validation check missing for new version or major version mismatch  
-**Solution**: Ensure the validation check for your version is added to generate.yml and the major version in your config matches the expected value
+**Cause**: ConfigValidator not updated with new version or major version mismatch  
+**Solution**: Ensure the new version is added to `SUPPORTED_VERSIONS` in `.github/config_validator.rb` and the major version in your config file matches the expected value
 
 ### Generated version is 2.x.x or 3.x.x instead of 4.0.0
 **Cause**: Wrong major version in config file  
 **Solution**: Update `npmVersion: 4.0.0` in config file to use unique major version
 
 ### generate_publish_release.yml doesn't recognize new version
-**Cause**: Version-to-config mapping missing in Setup job or ChangelogManager not updated  
-**Solution**: Verify two locations in generate_publish_release.yml are updated: (1) version-to-config mapping in Setup job, and (2) add version to API_VERSION_ORDER in changelog_manager.rb
+**Cause**: Version-to-config mapping missing in Setup job, ChangelogManager not updated, or ConfigValidator not updated  
+**Solution**: Verify three locations are updated: (1) version-to-config mapping in generate_publish_release.yml Setup job, (2) add version to `API_VERSION_ORDER` in `changelog_manager.rb`, and (3) add version to `SUPPORTED_VERSIONS` in `config_validator.rb`
 
 ### on-push-master.yml doesn't trigger after merge
 **Cause**: Path trigger syntax incorrect or matrix not updated  

docs/Multi-Version-SDK-Flow.md

@@ -2,7 +2,7 @@
 
 **Document Purpose**: Quick-reference guide to the multi-version SDK generation, publishing, and release system. This is your entry point to understanding how the system works.
 
-**Last Updated**: January 27, 2026  
+**Last Updated**: January 28, 2026  
 **Read Time**: 5-10 minutes  
 **Audience**: Anyone joining the team or needing a system overview