Skip to content

ci: sync GitHub Actions versions on main (checkout v4→v7, setup-node v4→v6)#3

Merged
jphan32 merged 1 commit into
mainfrom
ci/sync-action-versions
Jun 23, 2026
Merged

ci: sync GitHub Actions versions on main (checkout v4→v7, setup-node v4→v6)#3
jphan32 merged 1 commit into
mainfrom
ci/sync-action-versions

Conversation

@jphan32

@jphan32 jphan32 commented Jun 23, 2026

Copy link
Copy Markdown
Member

Summary

Follow-up to the Dependabot CI bumps that merged into dev (#1, #2). Those PRs
updated the GitHub Actions used by the workflows — but only on dev. main
still pinned the old majors in both ci.yml and release.yml:

  • actions/checkout v4 → v7
  • actions/setup-node v4 → v6

This keeps main's release pipeline running on the same, current action
versions Dependabot already validated on dev (CI green). After merge, main
and dev workflow files match exactly.

Why a separate PR (not waiting for the next release)

Per the git-flow model main only receives changes via PR. The bumps touch
release.yml, which runs on tags cut from main, so main should carry the
current versions independent of the next feature release.

Type of change

  • Docs / chore (CI only — no plugin code or behavior change)

How was this tested?

The identical versions are already running green on dev (push + the two
Dependabot PRs). CI (validate) runs on this PR as well.

Checklist

  • CI only; no main.js / styles.css / manifest.json change
  • validate workflow runs on this PR
  • main workflows will match dev after merge

Dependabot validated these action-version bumps on `dev` (PRs #1, #2, CI
green), but `main` still pinned v4 in both ci.yml and release.yml. Sync main
so its release pipeline runs on the same, current action versions as dev.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@jphan32
jphan32 merged commit c4f7674 into main Jun 23, 2026
1 check passed
@jphan32
jphan32 deleted the ci/sync-action-versions branch June 23, 2026 11:43
jphan32 added a commit that referenced this pull request Jun 23, 2026
chore: sync dev with main after PR #3 (git-flow back-merge)
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