From 845f1b44a5044b2cdb21a83dc171360c6a242418 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 31 Aug 2026 18:06:24 +0000 Subject: [PATCH] #45 chore: bring context-cadence's checkout up to v7 Dependabot's #34 rewrote the v4 pins in ci.yml and sdk-staleness.yml and left this one at v5, because it proposes one version transition at a time. The result was a repo pinning two majors of the same action, which is exactly the kind of split that goes unnoticed until one of them breaks. The v6 and v7 notes carry nothing this workflow depends on: v6 moved credentials to a separate file, v7 blocks fork checkout under pull_request_target and workflow_run, and this job runs on schedule and workflow_dispatch. submodules: recursive is untouched and still load-bearing. Co-Authored-By: Claude Opus 5 (1M context) --- .github/workflows/context-cadence.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/context-cadence.yml b/.github/workflows/context-cadence.yml index 47da4ec..0abff8c 100644 --- a/.github/workflows/context-cadence.yml +++ b/.github/workflows/context-cadence.yml @@ -49,7 +49,7 @@ jobs: # with a deprecation warning on every run. Twelve repos are about to adopt # this template, and sweeping twelve for a warning we could have not # written is the avoidable version of the problem (#163). - - uses: actions/checkout@v5 + - uses: actions/checkout@v7 with: submodules: recursive fetch-depth: 0