build: update checkout action to v6

[rejected-l]

Bumps actions/checkout from v5 to v6. Workflow-only change, no impact on functionality.

https://github.com/actions/checkout/releases/tag/v6.0.0

[vercel]

@rejected-l is attempting to deploy a commit to the Warden Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

📝 Walkthrough

Walkthrough

GitHub Actions workflow files across the repository have been updated to use actions/checkout@v6 instead of actions/checkout@v5. This is a straightforward version bump of the checkout action applied consistently across 19 workflow files. No workflow logic, control flow, or functionality has been altered.

Changes

Cohort / File(s)

Change Summary

GitHub Actions checkout version bump .github/workflows/automated-orders-relayer.yml, automated-orders-scheduler.yml, buf-ci.yaml, build_push.yml, changelog-reminder.yml, contracts.yml, go-client.yml, go-mod-tidy.yml, integration-tests.yml, keychain-sdk.yml, license.yml, release-docker-images.yml, release-wardend-binaries.yaml, scan-fs.yaml, shield.yml, soliditygen.yml, spaceward.yml, wardend.yaml, wardenkms.yml, warden/.github/workflows/release.yml

Updated actions/checkout from v5 to v6 in all checkout steps; all other workflow steps and logic remain unchanged

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Highly homogeneous changes across all files—identical version bump pattern repeated consistently
• No logic modifications, behavioral changes, or workflow restructuring
• Straightforward action version upgrade requiring minimal scrutiny per file
• Low risk of unintended side effects due to the narrowly scoped nature of the change

Possibly related PRs

• ci: bump actions/checkout to v4 #1462: Performs the same code-level change of updating actions/checkout version across GitHub Actions workflow files
• build: update checkout action to v5 #1661: Modifies the same GitHub Actions workflow checkout steps, upgrading actions/checkout versions in the same files
• ci: use different builders for different archs #1640: Updates CI workflow files including release-docker-images.yml and release-wardend-binaries.yml with similar action version changes

Suggested reviewers

• Pitasi
• jlehtimaki

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: upgrading the checkout action from v5 to v6 across multiple GitHub Actions workflows.
Description check	✅ Passed	The description is directly related to the changeset, explaining the version bump from v5 to v6 and noting it is workflow-only with no functional impact.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7944758 and 909fbb2.

📒 Files selected for processing (20)

• .github/workflows/automated-orders-relayer.yml (1 hunks)
• .github/workflows/automated-orders-scheduler.yml (1 hunks)
• .github/workflows/buf-ci.yaml (1 hunks)
• .github/workflows/build_push.yml (1 hunks)
• .github/workflows/changelog-reminder.yml (1 hunks)
• .github/workflows/contracts.yml (1 hunks)
• .github/workflows/go-client.yml (2 hunks)
• .github/workflows/go-mod-tidy.yml (1 hunks)
• .github/workflows/integration-tests.yml (1 hunks)
• .github/workflows/keychain-sdk.yml (2 hunks)
• .github/workflows/license.yml (1 hunks)
• .github/workflows/release-docker-images.yml (2 hunks)
• .github/workflows/release-wardend-binaries.yaml (2 hunks)
• .github/workflows/scan-fs.yaml (1 hunks)
• .github/workflows/shield.yml (2 hunks)
• .github/workflows/soliditygen.yml (2 hunks)
• .github/workflows/spaceward.yml (1 hunks)
• .github/workflows/wardend.yaml (2 hunks)
• .github/workflows/wardenkms.yml (2 hunks)
• warden/.github/workflows/release.yml (1 hunks)

🔇 Additional comments (26)

.github/workflows/build_push.yml (1)

33-33: Checkout version updated; no other Docker build steps affected.

The upgrade from v5 to v6 is isolated to the checkout step. Subsequent Docker build operations remain unchanged and should function identically given compatible checkout behavior.

.github/workflows/contracts.yml (1)

23-23: Checkout version bump maintains compatibility with downstream steps.

The upgrade from v5 to v6 is consistent with other workflows in the PR. Solidity test execution (foundry and pnpm) depends only on the checked-out source and should be unaffected by the checkout action version.

.github/workflows/wardenkms.yml (1)

27-27: Both lint and unit-test jobs updated consistently.

The checkout action is upgraded from v5 to v6 in both the lint job (line 27) and unit-test job (line 42). This consistent application across jobs is sound, and subsequent Go setup and build steps remain compatible.

Also applies to: 42-42

.github/workflows/scan-fs.yaml (1)

15-15: Clean version bump for vulnerability scanning workflow.

The checkout step is updated from v5 to v6 in this simple scanning workflow. The Trivy scanner operates on the checked-out filesystem and should be unaffected by the checkout action version.

.github/workflows/integration-tests.yml (1)

13-13: Version bump for scheduled integration tests.

The checkout is upgraded from v5 to v6. This scheduled workflow (every 4 hours) will continue to fetch source and run integration tests without issues, assuming checkout v6 maintains compatible behavior with v5.

.github/workflows/soliditygen.yml (1)

19-19: Consistent checkout upgrade across lint and unit-test jobs.

Both the lint (line 19) and unit-test (line 34) jobs in the soliditygen workflow are updated from v5 to v6. The consistent application across these jobs, combined with unchanged subsequent Go linting and testing steps, maintains workflow integrity.

Also applies to: 34-34

.github/workflows/license.yml (1)

25-25: Checkout version upgrade for license header validation.

The checkout is updated from v5 to v6. The downstream license header checker will continue to validate source files normally, independent of checkout action version (assuming compatible behavior).

.github/workflows/buf-ci.yaml (1)

28-28: Breaking change identified in actions/checkout v6—verify runner compatibility.

The web search revealed a breaking change in v6: credentials are now persisted to a file under $RUNNER_TEMP instead of the local git config. This requires Actions Runner v2.329.0 or newer for container/Docker scenarios.

Before merging, confirm:

• Your GitHub Actions runner is v2.329.0 or later (check in Actions job logs)
• The workflow doesn't run in container/Docker contexts with older runners
• Subsequent steps (like bufbuild/buf-action) don't depend on the old git config credential behavior

If your standard GitHub-hosted runners are up-to-date, the change is safe. Otherwise, update your runner infrastructure or revert to v5.

.github/workflows/automated-orders-relayer.yml (1)

31-31: Straightforward version bump approved.

The update from actions/checkout@v5 to actions/checkout@v6 is clean and consistent with the PR objectives. This requires a minimum Actions Runner version of v2.329.0 to access the persisted credentials for Docker container action scenarios—ensure your runner infrastructure meets this requirement if Docker container actions are in use.

warden/.github/workflows/release.yml (1)

22-24: Approved.

The checkout action version is updated to v6 while correctly preserving the fetch-depth: 0 configuration needed for release workflows.

.github/workflows/automated-orders-scheduler.yml (1)

33-33: Approved.

Clean version bump to actions/checkout@v6.

.github/workflows/changelog-reminder.yml (1)

16-16: Approved.

Consistent checkout version upgrade.

.github/workflows/go-client.yml (2)

19-19: Approved.

Checkout action upgraded to v6 in lint job.

---

34-34: Approved.

Checkout action upgraded to v6 in unit-test job.

.github/workflows/wardend.yaml (2)

32-32: Approved.

Checkout action upgraded to v6 in lint job.

---

47-47: Approved.

Checkout action upgraded to v6 in unit-test job.

.github/workflows/shield.yml (2)

19-19: Approved.

Checkout action upgraded to v6 in lint job.

---

34-34: Approved.

Checkout action upgraded to v6 in unit-test job.

.github/workflows/keychain-sdk.yml (2)

19-19: Approved.

Checkout action upgraded to v6 in lint job.

---

34-34: Approved.

Checkout action upgraded to v6 in unit-test job.

.github/workflows/go-mod-tidy.yml (1)

10-10: Straightforward version bump applied correctly.

The checkout action update from v5 to v6 is applied correctly with no configuration changes needed. This workflow has no special requirements that would be affected by the credential persistence changes in v6.

.github/workflows/release-wardend-binaries.yaml (2)

18-20: Consistent version bump with configuration preserved.

Both build jobs (amd64 and arm64) have been correctly updated to checkout@v6 with the fetch-depth: 0 parameter preserved. This configuration is necessary for release workflows to access full commit history.

---

47-49: Consistency confirmed across build-arm64 job.

The version bump and fetch-depth configuration are correctly applied here as well, matching the amd64 job pattern.

.github/workflows/spaceward.yml (1)

22-22: Version bump applied cleanly to build job.

The checkout action has been correctly updated to v6 with no configuration needed for this Node.js/pnpm-based workflow.

.github/workflows/release-docker-images.yml (2)

30-32: Correct upgrade with full history fetching enabled.

The checkout action has been properly updated to v6 in the amd64 release job, with fetch-depth: 0 preserved for accessing full Git history during Docker image builds.

---

64-66: Consistent version upgrade in arm64 release job.

The arm64 job mirrors the amd64 job correctly, with checkout@v6 and fetch-depth: 0 both properly configured.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Pitasi]

thanks!