Remove npm script and update demo docs to use renovate CLI directly

- Remove renovate:jest npm script from package.json
- Update demo documentation to be more general about renovate CLI usage
- Include example command with GitHub token setup
- Make documentation less specific to Jest, more broadly applicable

Author: loujaybee

backend/catalog/package.json

@@ -9,7 +9,6 @@
     "build": "tsc",
     "test": "jest",
     "setup": "./scripts/setup.sh",
-    "renovate:jest": "echo 'Creating Jest v30 pull request...' && cd /workspaces/gitpodflix-demo && RENOVATE_TOKEN=$GH_CLI_TOKEN renovate --platform=github gitpod-samples/gitpodflix-demo"
   },
   "dependencies": {
     "express": "^4.18.2",

demos/fixing-renovate-dependencies.md

@@ -6,38 +6,42 @@ This demo shows how to use Renovate to create pull requests for dependency updat
 
 - Access to a Gitpod environment with this repository
 - GitHub CLI token configured (`GH_CLI_TOKEN` environment variable)
-- Renovate CLI installed (included in the devcontainer)
+- Renovate CLI is pre-installed in the devcontainer
 
 ## Steps to Replicate
 
 ### 1. Create a Renovate Pull Request
 
-Navigate to the catalog service directory and run the renovate Jest command:
+The Renovate CLI is available in this environment and can be used to scan for dependency updates. The repository includes a `renovate.json` configuration that focuses on Jest dependencies.
+
+To create a pull request for dependency updates, you can run:
 
 ```bash
-cd backend/catalog
-npm run renovate:jest
-```
+# Set the GitHub token for Renovate
+export RENOVATE_TOKEN=$GH_CLI_TOKEN
 
-This command will:
+# Run Renovate to scan and create pull requests
+renovate --platform=github gitpod-samples/gitpodflix-demo
+```
 
+This will:
 - Use the existing `renovate.json` configuration
-- Create a pull request specifically for Jest dependency updates
-- Target Jest upgrades that may introduce breaking changes
+- Scan for dependency updates (currently configured for Jest)
+- Create pull requests for available updates
+- Target upgrades that may introduce breaking changes
 
 ### 2. Review the Pull Request
 
-After the command completes, check the GitHub repository for the newly created pull request. The PR will contain:
-
-- Updated Jest dependencies
-- Breaking changes that need to be addressed
+After the command completes, check the GitHub repository for newly created pull requests. The PRs will contain:
+- Updated dependencies
+- Changelog information about breaking changes
+- Details about what needs to be addressed
 
 ### 3. Resolve Breaking Changes with AI
 
 You have several options to get AI assistance for resolving the breaking changes:
 
 #### Option A: Using GitHub CLI
-
 ```bash
 # Get PR details and diff
 gh pr view <PR_NUMBER> --json body,title,files
@@ -47,23 +51,44 @@ gh pr diff <PR_NUMBER>
 ```
 
 #### Option B: Manual Context Gathering
-
 1. Copy the PR description and diff manually
 2. Include relevant test files that might be affected
-3. Construct a prompt asking for help with Jest migration
+3. Construct a prompt asking for help with dependency migration
 
 #### Option C: Direct File Analysis
-
 1. Review the failing tests after merging the PR
 2. Copy error messages and affected code
-3. Ask AI to help fix the deprecated Jest matchers
+3. Ask AI to help fix compatibility issues
 
 ## Example AI Prompt
 
 ```
-I have a Jest upgrade from v29 to v30 that's causing test failures due to deprecated matchers. Here are the failing tests:
+I have a dependency upgrade that's causing test failures due to breaking changes. Here are the failing tests and error messages:
 
 [Include test file contents and error messages]
 
-Please help me update the deprecated Jest matchers to their v30 equivalents.
+Please help me update the code to be compatible with the new version.
 ```
+
+## Renovate Configuration
+
+The repository includes a `renovate.json` file that can be customized to target specific dependencies or change update behavior. You can modify this configuration to:
+- Target different packages
+- Change update frequency
+- Adjust PR creation settings
+- Enable/disable specific dependency types
+
+## Expected Outcomes
+
+- Pull requests with dependency updates
+- Understanding of how to use AI to resolve breaking changes
+- Updated code compatible with new dependency versions
+- Successful test suite execution after fixes
+
+## Notes for Sales Engineers
+
+- This demonstrates real-world dependency management scenarios
+- Shows how AI can assist with breaking changes during upgrades
+- Highlights the importance of having good test coverage
+- Illustrates the collaborative workflow between automated tools and AI assistance
+- Renovate CLI provides flexibility for different scanning and update strategies