Skip to content

Bump CI actions to current majors, point dependabot at develop - #168

Merged
neuromechanist merged 1 commit into
developfrom
chore/dependency-bumps
Aug 21, 2026
Merged

Bump CI actions to current majors, point dependabot at develop#168
neuromechanist merged 1 commit into
developfrom
chore/dependency-bumps

Conversation

@neuromechanist

Copy link
Copy Markdown
Member

Clears five of the six stale dependabot PRs. All of them proposed the current major, so nothing needed rebasing, only applying:

Action Was Now PR
actions/checkout v6 v7 #153
codecov/codecov-action v5 v7 #152
actions/dependency-review-action v4 v5 #143
docker/login-action v3 v4 #133
docker/metadata-action v5 v6 #131

What actually changes

Every one of these majors is a Node 24 runtime bump, which GitHub-hosted runners already satisfy (runner >= 2.327.1). I read each release note for changes that touch how this repo calls them:

  • checkout v7 blocks checking out a fork PR head under pull_request_target or workflow_run (actions/checkout#2454). claude-code-review.yml does exactly that, so bumping it would silently disable fork-PR review. That one step stays on v6 with a comment. Worth noting the block exists for a reason: that job holds secrets and contents: write while checking out fork code, which is the classic privilege-escalation shape. The fix is to reconsider the fork lane, not the pin, so I left the lane alone rather than redesigning it here.
  • metadata-action v6 changed # handling in list inputs, preserving inline # while still supporting full-line comments. docker-build.yml only uses full-line comments in its tags list, so it is unaffected.
  • codecov-action v5 to v7 carries no input changes; token, files, flags, name, fail_ci_if_error, and verbose all still apply.

Dependabot now targets develop

All four ecosystems get target-branch: "develop". Dependabot was opening PRs against main, which is why six of them accumulated unmerged: the branching strategy sends changes through develop, so nobody was going to merge them where they sat.

The sixth PR

#134 (wrangler 4.71.0 to 4.94.0 in /workers) is not included. Its proposal is stale by 30 minor versions (wrangler is at 4.125.0), and it carries a package-lock.json update, which is dependabot's to maintain. With the config change above, dependabot will reopen it against develop at the current version.

Verification

559 unit tests pass, all 16 workflow YAML files parse, and CI on this PR exercises the bumped checkout, codecov-action, and dependency-review-action directly.

Applies the five stale dependabot proposals (#131, #133, #143, #152, #153),
all of which are still the current majors: checkout v7, codecov-action v7,
dependency-review-action v5, docker/login-action v4, docker/metadata-action v6.
Every one is a Node 24 runtime bump; the only behavioral change that touches
this repo is checkout v7 refusing to check out a fork PR head under
pull_request_target, so the claude-code-review fork lane stays on v6 with a
comment explaining why.

Dependabot now targets develop, matching the branching strategy, so its
future PRs stop landing on main.

Tested: 559 unit tests pass; all 16 workflow YAML files parse.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant