187 fix catalog validation errors (#190) #minor

* fix: Display validation errors from catalog API responses

The error handling now detects and displays the violations array format
returned by validation endpoints. Previously, these errors showed as
"Unknown error - No details" because the code only handled the standard
message/details format.

Closes #187

Co-Authored-By: Claude Opus 4.5 <[email protected]>

* add: document staging-to-main release PR process in CLAUDE.md

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

Co-Authored-By: Claude Opus 4.5 <[email protected]>

* fix: sync HISTORY.md to staging after release to prevent merge conflicts

After a release, HISTORY.md is updated on main but staging doesn't get the
update. This causes merge conflicts when feature branches (created from main)
are merged to staging.

This fix adds a step to the publish workflow that syncs HISTORY.md from main
to staging after each release.

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

Co-Authored-By: Claude Opus 4.5 <[email protected]>

* fix: avoid ARG_MAX limit by using GitHub expressions instead of env var

The GITHUB_CONTEXT env var containing toJson(github) was too large when
merging many commits, causing "Argument list too long" error.

Fixed by accessing pusher.name and pusher.email directly via GitHub
expressions instead of passing the entire context as an environment variable.

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

Co-Authored-By: Claude Opus 4.5 <[email protected]>

---------

Co-authored-by: Claude Opus 4.5 <[email protected]>

Author: jeff-schnitter

.github/workflows/publish.yml

@@ -66,18 +66,30 @@ jobs:
           git push
         fi
 
+    - name: Sync HISTORY.md to staging
+      run: |
+        # Sync the HISTORY.md update to staging to prevent merge conflicts
+        # when feature branches (created from main) are merged to staging
+        git fetch origin staging
+        git checkout staging
+        git checkout main -- HISTORY.md
+        if git diff --exit-code HISTORY.md; then
+          echo "staging HISTORY.md already up to date"
+        else
+          git add HISTORY.md
+          git commit -m "chore: sync HISTORY.md from main"
+          git push origin staging
+        fi
+        git checkout main
+
     - name: Git details about version
       id: git-details
-      env:
-        GITHUB_CONTEXT: ${{ toJson(github) }}
       run: |
          version=$(git describe --tags --abbrev=0)
          echo "VERSION=${version}" >> $GITHUB_ENV
          echo "VERSION=${version}" >> $GITHUB_OUTPUT
-         pusher=$(echo "$GITHUB_CONTEXT" | jq -r ".event.pusher.name")
-         email=$(echo "$GITHUB_CONTEXT" | jq -r ".event.pusher.email")
-         echo "PUSHER=${pusher}" >> $GITHUB_OUTPUT
-         echo "EMAIL=${email}" >> $GITHUB_OUTPUT
+         echo "PUSHER=${{ github.event.pusher.name }}" >> $GITHUB_OUTPUT
+         echo "EMAIL=${{ github.event.pusher.email }}" >> $GITHUB_OUTPUT
          echo "URL=https://pypi.org/project/cortexapps-cli/${version}/" >> $GITHUB_OUTPUT
 
     - name: Publish

CLAUDE.md

@@ -141,12 +141,18 @@ Use the GitHub-recommended format: `<issue-number>-<short-description>`
 
 ### Release Workflow
 1. Create feature branch for changes
-2. Merge to `staging` branch for testing
-3. Merge `staging` to `main` to trigger release
-4. Version bumping:
+2. Create PR to merge feature branch to `staging` for testing
+3. Create PR to merge `staging` to `main` to trigger release:
+   ```bash
+   gh pr create --base main --head staging --title "Release X.Y.Z: Description #patch|#minor|#major"
+   ```
+   - Include version number and brief description in title
+   - Use `#patch`, `#minor`, or `#major` in the title to control version bump
+   - List all changes in the PR body
+4. Version bumping (based on hashtag in PR title or commit message):
    - Default: Patch version bump
-   - `#minor` in commit message: Minor version bump
-   - `#major` in commit message: Major version bump
+   - `#minor`: Minor version bump
+   - `#major`: Major version bump
 5. Release publishes to:
    - PyPI
    - Docker Hub (`cortexapp/cli:VERSION` and `cortexapp/cli:latest`)

cortexapps_cli/cortex_client.py

@@ -149,6 +149,23 @@ def request(self, method, endpoint, params={}, headers={}, data=None, raw_body=F
                 # try to parse the error message
                 error = response.json()
                 status = response.status_code
+
+                # Check for validation error format with violations array
+                if 'violations' in error and isinstance(error['violations'], list):
+                    print(f'[red][bold]HTTP Error {status}[/bold][/red]: Validation failed')
+                    for violation in error['violations']:
+                        title = violation.get('title', 'Validation Error')
+                        description = violation.get('description', 'No description')
+                        violation_type = violation.get('violationType', '')
+                        pointer = violation.get('pointer', '')
+                        print(f'  [yellow]{title}[/yellow]: {description}')
+                        if pointer:
+                            print(f'    [dim]Location: {pointer}[/dim]')
+                        if violation_type:
+                            print(f'    [dim]Type: {violation_type}[/dim]')
+                    raise typer.Exit(code=1)
+
+                # Standard error format with message/details
                 message = error.get('message', 'Unknown error')
                 details = error.get('details', 'No details')
                 request_id = error.get('requestId', 'No request ID')