[actions] Update GitHub Actions versions - 2026-06-13

- github/gh-aw/actions/setup-cli: v0.78.3 → v0.79.8
- microsoft/apm-action: SHA update (v1.9.1)
- ruby/setup-ruby: v1.310.0 → v1.313.0
- Update workflows from source: ci-doctor, daily-team-status, dependabot-repair

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Author: Copilot

.github/aw/actions-lock.json

@@ -150,10 +150,10 @@
       "version": "v4.36.2",
       "sha": "8aad20d150bbac5944a9f9d289da16a4b0d87c1e"
     },
-    "github/gh-aw/actions/setup-cli@v0.78.3": {
+    "github/gh-aw/actions/setup-cli@v0.79.8": {
       "repo": "github/gh-aw/actions/setup-cli",
-      "version": "v0.78.3",
-      "sha": "544dd7355d846f9a7a1a5817a18148442e9ffe35"
+      "version": "v0.79.8",
+      "sha": "8b02ab336d100a5746e9f53b8bc2b22878278a6f"
     },
     "github/stale-repos@v9.0.14": {
       "repo": "github/stale-repos",
@@ -168,17 +168,17 @@
     "microsoft/apm-action@v1.9.1": {
       "repo": "microsoft/apm-action",
       "version": "v1.9.1",
-      "sha": "ce02c22416172beb70072c5910b2163ee3f006f6"
+      "sha": "e5650fb81c4b5965090a17bd1ed1956071e95d17"
     },
     "oven-sh/setup-bun@v2.2.0": {
       "repo": "oven-sh/setup-bun",
       "version": "v2.2.0",
       "sha": "0c5077e51419868618aeaa5fe8019c62421857d6"
     },
-    "ruby/setup-ruby@v1.310.0": {
+    "ruby/setup-ruby@v1.313.0": {
       "repo": "ruby/setup-ruby",
-      "version": "v1.310.0",
-      "sha": "afeafc3d1ab54a631816aba4c914a0081c12ff2f"
+      "version": "v1.313.0",
+      "sha": "89f90524b88a01fe6e0b732220432cc6142926af"
     },
     "safedep/pmg@v1": {
       "repo": "safedep/pmg",

.github/workflows/ci-doctor.md

@@ -1,7 +1,18 @@
 ---
+<<<<<<< current (local changes)
 emoji: "🏥"
 description: Investigates failed CI workflows to identify root causes and patterns, creating issues with diagnostic information; also reviews PR check failures when the ci-doctor label is applied
+||||||| base (original)
+=======
+description: |
+  This workflow is an automated CI failure investigator that triggers when monitored workflows fail.
+  Performs deep analysis of GitHub Actions workflow failures to identify root causes,
+  patterns, and provide actionable remediation steps. Analyzes logs, error messages,
+  and workflow configuration to help diagnose and resolve CI issues efficiently.
+
+>>>>>>> new (upstream)
 on:
+<<<<<<< current (local changes)
   label_command:
     name: ci-doctor
     events: [pull_request]
@@ -14,17 +25,52 @@ permissions:
   issues: read          # To search and analyze issues (label removal handled by activation job)
   pull-requests: read   # To read PR context (comments posted via safe-outputs)
   checks: read          # To read check run results
+||||||| base (original)
+  workflow_run:
+    workflows: ["Daily Perf Improver", "Daily Test Coverage Improver"]  # Monitor the CI workflow specifically
+    types:
+      - completed
+    branches:
+      - main
+    # This will trigger only when the CI workflow completes with failure
+    # The condition is handled in the workflow body
+  stop-after: +1mo
+
+# Only trigger for failures - check in the workflow body
+if: ${{ github.event.workflow_run.conclusion == 'failure' }}
+
+permissions: read-all
+=======
+  workflow_run:
+    workflows: ["Daily Perf Improver", "Daily Test Coverage Improver"]  # Monitor the CI workflow specifically
+    types:
+      - completed
+    branches:
+      - main
+
+# Only trigger for failures - check in the workflow body
+if: ${{ github.event.workflow_run.conclusion == 'failure' }}
+
+permissions: read-all
+>>>>>>> new (upstream)
 
 network: defaults
 
 engine: claude
 
 safe-outputs:
   create-issue:
+<<<<<<< current (local changes)
     expires: 1d
     title-prefix: "[CI Failure Doctor] "
     labels: [cookie]
     close-older-issues: true
+||||||| base (original)
+    title-prefix: "${{ github.workflow }}"
+=======
+    title-prefix: "[ci-doctor] "
+    labels: [automation, ci]
+>>>>>>> new (upstream)
   add-comment:
     max: 1
     hide-older-comments: true
@@ -42,6 +88,7 @@ tools:
   cli-proxy: true
   cache-memory: true
   web-fetch:
+<<<<<<< current (local changes)
   web-search:
   github:
     mode: gh-proxy
@@ -202,13 +249,28 @@ steps:
 
       echo ""
       echo "✅ PR pre-analysis complete. Agent should start with $SUMMARY_FILE"
+||||||| base (original)
+  web-search:
+
+timeout-minutes: 10
+=======
 
+timeout-minutes: 10
+>>>>>>> new (upstream)
+
+<<<<<<< current (local changes)
 source: githubnext/agentics/workflows/ci-doctor.md@ea350161ad5dcc9624cf510f134c6a9e39a6f94d
 
+||||||| base (original)
+source: githubnext/agentics/workflows/ci-doctor.md@ea350161ad5dcc9624cf510f134c6a9e39a6f94d
+=======
+source: githubnext/agentics/workflows/ci-doctor.md@e15e57b40918dbca11b350c55d02ab61934afa75
+>>>>>>> new (upstream)
 ---
 
 # CI Failure Doctor
 
+<<<<<<< current (local changes)
 You are the CI Failure Doctor, an expert investigative agent that analyzes failed GitHub Actions checks to identify root causes and patterns. You operate in one of two modes depending on the trigger:
 
 - **PR Check Review Mode** — triggered when someone applies the `ci-doctor` label to a pull request; reviews the PR's failing CI checks and posts a diagnostic comment.
@@ -294,6 +356,11 @@ Check run data was fetched before this session:
 {{/if}}
 {{#if github.event.workflow_run.id}}
 ## CI Failure Investigation Mode
+||||||| base (original)
+You are the CI Failure Doctor, an expert investigative agent that analyzes failed GitHub Actions workflows to identify root causes and patterns. Your mission is to conduct a deep investigation when the CI workflow fails.
+=======
+You are the CI Failure Doctor, an expert investigative agent that analyzes failed GitHub Actions workflows to identify root causes and patterns. Your goal is to conduct a deep investigation when the CI workflow fails.
+>>>>>>> new (upstream)
 
 ## Current Context
 
@@ -320,21 +387,42 @@ Logs and artifacts have been pre-downloaded before this session started:
 **ONLY proceed if the workflow conclusion is 'failure' or 'cancelled'**. If the workflow was successful, **call the `noop` tool** immediately and exit.
 
 ### Phase 1: Initial Triage
+
 1. **Verify Failure**: Check that `${{ github.event.workflow_run.conclusion }}` is `failure` or `cancelled`
+<<<<<<< current (local changes)
    - **If the workflow was successful**: Call the `noop` tool with message "CI workflow completed successfully - no investigation needed" and **stop immediately**. Do not proceed with any further analysis.
    - **If the workflow failed or was cancelled**: Proceed with the investigation steps below.
 2. **Get Workflow Details**: Use `get_workflow_run` to get full details of the failed run
 3. **List Jobs**: Use `list_workflow_jobs` to identify which specific jobs failed
 4. **Quick Assessment**: Determine if this is a new type of failure or a recurring pattern
+||||||| base (original)
+2. **Get Workflow Details**: Use `get_workflow_run` to get full details of the failed run
+3. **List Jobs**: Use `list_workflow_jobs` to identify which specific jobs failed
+4. **Quick Assessment**: Determine if this is a new type of failure or a recurring pattern
+=======
+2. **Deduplication Check**: Read `/tmp/memory/investigations/analyzed-runs.json` from the cache. If the current run ID (`${{ github.event.workflow_run.id }}`) is already listed, **stop immediately** — this run has already been investigated. After completing a new investigation, append the run ID to this index to prevent re-analysis.
+3. **Get Workflow Details**: Use `get_workflow_run` to get full details of the failed run
+4. **List Jobs**: Use `list_workflow_jobs` to identify which specific jobs failed
+5. **Quick Assessment**: Determine if this is a new type of failure or a recurring pattern
+>>>>>>> new (upstream)
 
 ### Phase 2: Deep Log Analysis
+<<<<<<< current (local changes)
 1. **Use Pre-Downloaded Logs and Artifacts**: Use the files in `/tmp/gh-aw/agent/ci-doctor/`:
    - Read the summary and hint files first (minimal context load)
    - Read ±10 lines around each hinted line number in the full log or artifact file
    - Check `/tmp/gh-aw/agent/ci-doctor/artifacts/` for any structured output (test reports, coverage, etc.)
    - Only load the full log content if the hints are insufficient
 2. **Fallback Log Retrieval**: If pre-downloaded files are unavailable, use `get_job_logs` with `failed_only=true`, `return_content=true`, and `tail_lines=100` to get the most relevant portion of logs directly (avoids downloading large blob files). Do NOT use `web-fetch` on blob storage log URLs.
 3. **Pattern Recognition**: Analyze logs for:
+||||||| base (original)
+1. **Retrieve Logs**: Use `get_job_logs` with `failed_only=true` to get logs from all failed jobs
+2. **Pattern Recognition**: Analyze logs for:
+=======
+
+1. **Retrieve Logs**: Use `get_job_logs` with `failed_only=true` to get logs from all failed jobs
+2. **Pattern Recognition**: Analyze logs for:
+>>>>>>> new (upstream)
    - Error messages and stack traces
    - Dependency installation failures
    - Test failures with specific patterns
@@ -349,6 +437,7 @@ Logs and artifacts have been pre-downloaded before this session started:
    - Timing patterns
 
 ### Phase 3: Historical Context Analysis
+
 1. **Search Investigation History**: Use file-based storage to search for similar failures:
    - Read from cached investigation files in `/tmp/gh-aw/agent/memory/investigations/`
    - Parse previous failure patterns and solutions
@@ -358,6 +447,7 @@ Logs and artifacts have been pre-downloaded before this session started:
 4. **PR Context**: If triggered by a PR, analyze the changed files
 
 ### Phase 4: Root Cause Investigation
+
 1. **Categorize Failure Type**:
    - **Code Issues**: Syntax errors, logic bugs, test failures
    - **Infrastructure**: Runner issues, network problems, resource constraints
@@ -373,6 +463,7 @@ Logs and artifacts have been pre-downloaded before this session started:
    - For timeout issues: Identify slow operations and bottlenecks
 
 ### Phase 5: Pattern Storage and Knowledge Building
+
 1. **Store Investigation**: Save structured investigation data to files:
    - Write investigation report to `/tmp/gh-aw/agent/memory/investigations/<timestamp>-<run-id>.json`
      - **Important**: Use filesystem-safe timestamp format `YYYY-MM-DD-HH-MM-SS-sss` (e.g., `2026-02-12-11-20-45-458`)
@@ -382,6 +473,7 @@ Logs and artifacts have been pre-downloaded before this session started:
 2. **Update Pattern Database**: Enhance knowledge with new findings by updating pattern files
 3. **Save Artifacts**: Store detailed logs and analysis in the cached directories
 
+<<<<<<< current (local changes)
 ### Phase 6: Looking for existing issues and closing older ones
 
 1. **Search for existing CI failure doctor issues**
@@ -407,6 +499,35 @@ Logs and artifacts have been pre-downloaded before this session started:
     - Otherwise, continue to create a new issue with fresh investigation data
 
 ### Phase 7: Reporting and Recommendations
+||||||| base (original)
+### Phase 6: Looking for existing issues
+
+1. **Convert the report to a search query**
+    - Use any advanced search features in GitHub Issues to find related issues
+    - Look for keywords, error messages, and patterns in existing issues
+2. **Judge each match issues for relevance**
+    - Analyze the content of the issues found by the search and judge if they are similar to this issue.
+3. **Add issue comment to duplicate issue and finish**
+    - If you find a duplicate issue, add a comment with your findings and close the investigation.
+    - Do NOT open a new issue since you found a duplicate already (skip next phases).
+
+### Phase 6: Reporting and Recommendations
+=======
+### Phase 6: Looking for existing issues
+
+1. **Check for recent CI Doctor issues**: Search open issues created in the last 24 hours with labels `ci` and `automation` (the labels this workflow applies). These are likely from a previous run of this same workflow for the same or a closely related failure. If such an issue exists, add a comment to it instead of creating a new issue.
+2. **Convert the report to a search query**
+    - Use any advanced search features in GitHub Issues to find related issues
+    - Look for keywords, error messages, and patterns in existing issues
+3. **Judge each match for relevance**
+    - Analyze the content of the issues found by the search and judge if they are similar to this issue.
+4. **Add issue comment to duplicate issue and finish**
+    - If you find a duplicate issue, add a comment with your findings and close the investigation.
+    - Do NOT open a new issue since you found a duplicate already (skip next phases).
+
+### Phase 7: Reporting and Recommendations
+
+>>>>>>> new (upstream)
 1. **Create Investigation Report**: Generate a comprehensive analysis including:
    - **Executive Summary**: Quick overview of the failure
    - **Root Cause**: Detailed explanation of what went wrong

.github/workflows/daily-team-status.md

@@ -1,54 +1,43 @@
 ---
-emoji: "📅"
-timeout-minutes: 10
-strict: true
+description: |
+  This workflow is a daily team status reporter creating upbeat activity summaries.
+  Gathers recent repository activity (issues, PRs, discussions, releases, code changes)
+  and generates engaging GitHub issues with productivity insights, community
+  highlights, and project recommendations. Uses a positive, encouraging tone with
+  moderate emoji usage to boost team morale.
+
 on:
-  schedule:
-  - cron: "daily around 9:00 on weekdays"
-  stop-after: +1mo
-  workflow_dispatch: null
+  schedule: daily
+  workflow_dispatch:
+
 permissions:
   contents: read
   issues: read
   pull-requests: read
-tracker-id: daily-team-status
+
 network: defaults
-imports:
-  - uses: shared/daily-audit-base.md
-    with:
-      title-prefix: "[team-status] "
-      expires: 1d
-  - shared/otlp.md
+
+tools:
+  github:
+    min-integrity: none # This workflow is allowed to examine and comment on any issues
+
 safe-outputs:
+  mentions: false
+  allowed-github-references: []
   create-issue:
-    expires: 1d
     title-prefix: "[team-status] "
-    labels: [automation, daily-report]
-description: |
-  This workflow created daily team status reporter creating upbeat activity summaries.
-  Gathers recent repository activity (issues, PRs, releases, code changes)
-  and generates engaging GitHub issues with productivity insights, community
-  highlights, and project recommendations. Uses a positive, encouraging tone with
-  moderate emoji usage to boost team morale.
-source: githubnext/agentics/workflows/daily-team-status.md@d3422bf940923ef1d43db5559652b8e1e71869f3
-tools:
-  cli-proxy: true
-  github: null
-
-
+    labels: [report, daily-status]
+    close-older-issues: true
+source: githubnext/agentics/workflows/team-status.md@main
 ---
 
-{{#runtime-import? .github/shared-instructions.md}}
-
-{{#runtime-import .github/shared/editorial.md}}
-
-# Daily Team Status
+# Team Status
 
 Create an upbeat daily status report for the team as a GitHub issue.
 
 ## What to include
 
-- Recent repository activity (issues, PRs, releases, code changes)
+- Recent repository activity (issues, PRs, discussions, releases, code changes)
 - Team productivity suggestions and improvement ideas
 - Community engagement highlights
 - Project investment and feature recommendations
@@ -63,5 +52,3 @@ Create an upbeat daily status report for the team as a GitHub issue.
 
 1. Gather recent activity from the repository
 2. Create a new GitHub issue with your findings and insights
-
-{{#runtime-import shared/noop-reminder.md}}