ci: sync GitHub Actions versions on main (checkout v4→v7, setup-node v4→v6)#3
Merged
Conversation
3 tasks
jphan32
added a commit
that referenced
this pull request
Jun 23, 2026
chore: sync dev with main after PR #3 (git-flow back-merge)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to the Dependabot CI bumps that merged into
dev(#1, #2). Those PRsupdated the GitHub Actions used by the workflows — but only on
dev.mainstill pinned the old majors in both
ci.ymlandrelease.yml:actions/checkoutv4 → v7actions/setup-nodev4 → v6This keeps
main's release pipeline running on the same, current actionversions Dependabot already validated on
dev(CI green). After merge,mainand
devworkflow files match exactly.Why a separate PR (not waiting for the next release)
Per the git-flow model
mainonly receives changes via PR. The bumps touchrelease.yml, which runs on tags cut frommain, somainshould carry thecurrent versions independent of the next feature release.
Type of change
How was this tested?
The identical versions are already running green on
dev(push + the twoDependabot PRs). CI (
validate) runs on this PR as well.Checklist
main.js/styles.css/manifest.jsonchangevalidateworkflow runs on this PRmainworkflows will matchdevafter merge