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

[dependabot]

Bumps actions/checkout from 4 to 6.

Release notes

Sourced from actions/checkout's releases.

v6.0.0

What's Changed

• Update README to include Node.js 24 support details and requirements by @​salmanmkc in actions/checkout#2248
• Persist creds to a separate file by @​ericsciple in actions/checkout#2286
• v6-beta by @​ericsciple in actions/checkout#2298
• update readme/changelog for v6 by @​ericsciple in actions/checkout#2311

Full Changelog: actions/checkout@v5.0.0...v6.0.0

v6-beta

What's Changed

Updated persist-credentials to store the credentials under $RUNNER_TEMP instead of directly in the local git config.

This requires a minimum Actions Runner version of v2.329.0 to access the persisted credentials for Docker container action scenarios.

v5.0.1

What's Changed

• Port v6 cleanup to v5 by @​ericsciple in actions/checkout#2301

Full Changelog: actions/checkout@v5...v5.0.1

v5.0.0

What's Changed

• Update actions checkout to use node 24 by @​salmanmkc in actions/checkout#2226
• Prepare v5.0.0 release by @​salmanmkc in actions/checkout#2238

⚠️ Minimum Compatible Runner Version

v2.327.1
Release Notes

Make sure your runner is updated to this version or newer to use this release.

Full Changelog: actions/checkout@v4...v5.0.0

v4.3.1

What's Changed

• Port v6 cleanup to v4 by @​ericsciple in actions/checkout#2305

Full Changelog: actions/checkout@v4...v4.3.1

v4.3.0

What's Changed

• docs: update README.md by @​motss in actions/checkout#1971
• Add internal repos for checking out multiple repositories by @​mouismail in actions/checkout#1977
• Documentation update - add recommended permissions to Readme by @​benwells in actions/checkout#2043

... (truncated)

Commits

• 8e8c483 Clarify v6 README (#2328)
• 033fa0d Add worktree support for persist-credentials includeIf (#2327)
• c2d88d3 Update all references from v5 and v4 to v6 (#2314)
• 1af3b93 update readme/changelog for v6 (#2311)
• 71cf226 v6-beta (#2298)
• 069c695 Persist creds to a separate file (#2286)
• ff7abcd Update README to include Node.js 24 support details and requirements (#2248)
• 08c6903 Prepare v5.0.0 release (#2238)
• 9f26565 Update actions checkout to use node 24 (#2226)
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[jbdevprimary]

🔧 CI Fix Suggestion

Branch: dependabot/github_actions/actions/checkout-6

1. Root Cause

The download-artifact step failed because an artifact named build-output was not found in the specified workflow run. This is typically caused by a name mismatch between the upload-artifact and download-artifact steps or because the uploading job failed.

2. Suggested Fix

Ensure the upload-artifact and download-artifact steps use the exact same name and that the download job depends on the successful completion of the upload job.

In your workflow file (.github/workflows/*.yml):

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Upload build artifact
        uses: actions/upload-artifact@v4
        with:
          name: build-output # Must match download name
          path: dist/         # Path to files to upload

  deploy:
    needs: build # Ensures 'build' job succeeds first
    runs-on: ubuntu-latest
    steps:
      - name: Download build artifact
        uses: actions/download-artifact@v4
        with:
          name: build-output # Must match upload name
          path: dist         # Path to download files into

If you must download from a previous workflow run, verify that run 20614537501 completed successfully and uploaded an artifact with the exact name build-output.

3. Commands to Verify the Fix

1. Push the corrected workflow file to your repository to trigger a new run.
2. Navigate to the "Actions" tab in your GitHub repository.
3. In the new workflow run, check that the build job completes successfully and uploads the artifact.
4. Confirm the subsequent deploy job now passes the download-artifact step.

---

_{🤖 Generated by Ecosystem Fixer using Ollama GLM 4.6}

[jbdevprimary]

🔧 CI Fix Suggestion

Branch: dependabot/github_actions/actions/checkout-6

1. Root cause:
   The download-artifact action failed because the artifact named build-output was not found in the specified workflow run (run-id: 20614593549). This indicates that the preceding upload step for this artifact either failed, was not run, or the artifact has a different name or has expired.

2. Suggested fix:
   Ensure a step in the same or a previous workflow job uses actions/upload-artifact@v4 to upload an artifact named build-output.

# In the job that produces the artifact (e.g., 'build')
- name: Upload build artifacts
  uses: actions/upload-artifact@v4
  with:
    name: build-output
    path: path/to/your/dist

Also, verify the run-id in the download step correctly targets a workflow run that actually created and uploaded the artifact. Use github.run_id to download from the current workflow run if possible.

# In the downloading job
- name: Download build artifacts
  uses: actions/download-artifact@v4
  with:
    name: build-output
    path: dist
    # run-id: github.run_id # Optional, only if downloading from a different run

3. Commands to verify the fix:
   After merging the fix and triggering a new workflow run:
4. Check the logs of the job that uploads the artifact to confirm "Upload build artifacts" was successful.
5. Check the logs of the job that downloads the artifact to confirm it successfully found and downloaded build-output. The error message Unable to download artifact(s): Artifact not found should be gone.

---

_{🤖 Generated by Ecosystem Fixer using Ollama GLM 4.6}

[jbdevprimary]

🔧 CI Fix Suggestion

Branch: dependabot/github_actions/actions/checkout-6

1. Root Cause

The CI job is trying to download an artifact named build-output from a previous workflow run, but that artifact does not exist. The previous job either failed to upload the artifact, used a different name, or the artifact has expired.

2. Suggested Fix

Ensure the job uploading the artifact succeeds and that the name parameter matches exactly between your upload-artifact and download-artifact steps. Also, make sure the download job correctly depends on the upload job using the needs keyword.

Example Fix:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      # ... steps that create a 'dist' directory
      - name: Upload build artifacts
        uses: actions/upload-artifact@v4
        with:
          name: build-output # <--- Must match download name
          path: ./dist

  test:
    needs: build # <--- Ensures 'build' job runs first
    runs-on: ubuntu-latest
    steps:
      - name: Download build artifacts
        uses: actions/download-artifact@v4
        with:
          name: build-output # <--- Must match upload name
          path: dist

3. Commands to Verify the Fix

1. Inspect the Uploader Job: Go to the "Actions" tab in your GitHub repository, find the workflow run with ID 20616111762, and check the logs of the job that was supposed to upload build-output. Verify that the upload-artifact step ran without error.
2. name: Upload and the uploader job completed successfully.

** upload and the artifact name is correct with the needs to verify and the artifact has a.k
[download-art.

" upload-artifact' needs to match both have run.

1.

[1.</think>
###  'needs`   Run actions/download-artifact`/download-artifact
        -name: upload-artifact

[`
        name:**
```yaml
          with this is the exact same

[...]

        -name `needs: a`download-artifact`

### Steps and path: build-artifacts`

### Step: artifact

### [error]artifact is not found the same name between actions.

#### Steps to fix and match

### [error] with artifact names in the workflow.

### Steps to fix:

### Actions (upload-artifact needs: build`

### Commands to build name: path: name: download-artifact

### The error is a mismatch.

### The fix is the artifact path: name: name: path: path: path: path: actions path and path: build-artifacts path

### Steps to match the names of the artifacts.

### Root Cause
### Suggested name: artifacts path
### Commands to download
### Actions (upload-artifact needs: name: name.1. The artifact name is a mismatch.

### Fix

```yaml
# Workflow syntax to match names
- name: Upload artifacts
  uses: actions/upload-artifact@v4
  with:
    name: build-output
    path: ./dist

Commands to verify

# Check the run and compare names
gh run view 20616111762 --repo agentic-dev-library/control --log

2. Verify Workflow Syntax: Check your .github/workflows/main.yml (or similar file) and confirm that the job downloading the artifact includes needs: <name-of-uploading-job> and that the artifact name (build-output) is spelled identically in both the upload-artifact and download-artifact steps.

---

_{🤖 Generated by Ecosystem Fixer using Ollama GLM 4.6}

[jbdevprimary]

🔧 CI Fix Suggestion

Branch: dependabot/github_actions/actions/checkout-6

1. Root cause: The download-artifact step failed because it could not find an artifact named build-output. This indicates a mismatch or failure in the corresponding upload-artifact step from a previous job in the workflow.

2. Suggested fix: In the preceding workflow job, ensure the upload-artifact step is present and uses the exact same artifact name. The step should look like this:

   - name: Upload artifact
     uses: actions/upload-artifact@v4
     with:
       name: build-output
       path: dist

3. Commands to verify the fix:

   • Inspect your workflow file (e.g., .github/workflows/main.yml) to ensure the upload-artifact step uses name: build-output.
   • Re-run the workflow and check the Actions tab on GitHub to confirm the artifact is successfully uploaded in the first job before the download job starts.

---

_{🤖 Generated by Ecosystem Fixer using Ollama GLM 4.6}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jbdevprimary]

🔧 CI Fix Suggestion

Branch: dependabot/github_actions/actions/checkout-6

1. Root cause: The download step failed because the required artifact named build-output was never successfully created or uploaded by a previous job in the workflow. The log specifically shows a v3 version of download-artifact, which may be incompatible with an uploader using v4.

2. Suggested fix:

   • First, check the logs of the job that builds and uploads the artifact in the workflow run with ID 20634001417. It likely failed before it could upload the artifact.
   • Ensure the upload-artifact and download-artifact actions use compatible major versions. Update both to v4 to resolve potential incompatibilities.

   In your workflow file (.github/workflows/*.yml), change:

   # Old version
   - uses: actions/upload-artifact@v3
   - uses: actions/download-artifact@v3

   to:

   # New, compatible version
   - uses: actions/upload-artifact@v4
   - uses: actions/download-artifact@v4

3. Commands to verify the fix:

   1. In your GitHub repository, go to the Actions tab.
   2. Find the workflow run with ID 20634001417 and check the logs for the build/upload job to see why it failed.
   3. After applying the fix, re-run the workflow. Verify that the build job uploads the build-output artifact and that the subsequent download job completes successfully.

---

_{🤖 Generated by Ecosystem Fixer using Ollama GLM 4.6}

[jbdevprimary]

🔧 CI Fix Suggestion

Branch: dependabot/github_actions/actions/checkout-6

1. Root Cause: The workflow run failed because the specified run-id did not successfully upload an artifact named build-output. The download action is failing because the artifact it is looking for was never created or has already expired.

2. Suggested Fix: In the job that generates the files, ensure your upload-artifact step uses the exact same name (build-output) and a compatible version of the action. The name must match perfectly.

   # In the workflow job that builds and uploads the artifact
   - name: Upload build artifacts
     uses: actions/upload-artifact@v3 # Use the same major version as download-artifact
     with:
       name: build-output # This name must match the download step
       path: dist/         # The directory containing the files you want to upload

3. Commands to Verify: Navigate to the Actions tab in your GitHub repository. Find the specific workflow run that created the artifact (run-id: 20634012359) and check the logs for the upload-artifact step. Confirm it ran successfully without errors and uploaded an artifact with the correct name.

---

_{🤖 Generated by Ecosystem Fixer using Ollama GLM 4.6}