chore(deps): bump actions/checkout from 4 to 5

.github/workflows/ai-summary.yml

@@ -43,7 +43,7 @@ jobs:
       # This is required to access repository files and configuration
       # though for this workflow we don't directly use repository content
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       # Step 2: Generate AI summary using GitHub's AI inference API
       # This step processes the issue title and body to create a concise summary

.github/workflows/build.yml

@@ -42,7 +42,7 @@ jobs:
       # This step clones the repository code to the GitHub Actions runner
       # We set fetch-depth: 0 to get the complete history for versioning tools
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           fetch-depth: 0  # Fetch all history for all branches and tags
 

.github/workflows/pr-assignment.yml

@@ -112,7 +112,7 @@ jobs:
       # Step 1: Check out the repository to access CODEOWNERS file
       # We need the full repository content to properly analyze ownership rules
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           fetch-depth: 0  # Full history to ensure we have all necessary files
 

.github/workflows/pr-backmerge.yml

@@ -35,7 +35,7 @@ jobs:
     steps:
       # Step 1: Check out the repository code with full history
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           fetch-depth: 0 # Fetch all history for proper branch comparison
 

.github/workflows/pr-static-checks.yml

@@ -40,7 +40,7 @@ jobs:
       # Step 1: Check out the repository code
       # This gets the latest code from the pull request for analysis
       - name: Checkout code
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       # Step 2: Set up Node.js environment
       # Using Node.js 20 for compatibility with modern JavaScript features

.github/workflows/release.yml

@@ -46,7 +46,7 @@ jobs:
       # Step 1: Check out the repository code
       # This gets the latest code from the main branch
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       # Step 2: Fetch complete git history for accurate versioning
       # Auto requires full history to determine the correct version bump

.github/workflows/security.yml

@@ -107,7 +107,7 @@ jobs:
     steps:
     # Step 1: Check out the repository code for analysis
     - name: Checkout repository
-      uses: actions/checkout@v4
+      uses: actions/checkout@v5
 
     # Step 2: Initialize the CodeQL analysis engine
     # This sets up the CodeQL database and prepares for code scanning
@@ -142,7 +142,7 @@ jobs:
     steps:
       # Step 1: Check out the repository code for scanning
       - name: Checkout code
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       # Step 2: Run Trivy scanner to identify vulnerabilities in dependencies
       # Trivy is a comprehensive vulnerability scanner that can detect issues in
@@ -176,7 +176,7 @@ jobs:
       # Complete git history is required to detect secrets that may have been
       # committed in the past and still pose a security risk
       - name: Checkout Code
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           fetch-depth: 0  # Full history needed for accurate secret detection across all commits
           # No need for --unshallow as fetch-depth: 0 already gets the complete history
@@ -205,7 +205,7 @@ jobs:
     steps:
       # Step 1: Check out the repository code
       - name: Checkout Code
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       # Step 2: Build the Docker image for scanning if a Dockerfile exists
       # This creates a local image that will be analyzed for vulnerabilities