[TASK] Update GitHub Actions to latest versions - #1329
Closed
CybotTM wants to merge 1 commit into
Closed
Conversation
Updates the pinned actions in the six non-main workflows to their latest releases (SHAs verified against the GitHub API): - actions/checkout v6.0.2 -> v7.0.0 - actions/cache v5.0.3 -> v6.1.0 - dependabot/fetch-metadata v2.3.0 -> v3.1.0 - docker/build-push-action v7.0.0 -> v7.3.0 - docker/login-action v4.0.0 -> v4.4.0 - docker/metadata-action v6.0.0 -> v6.2.0 - docker/setup-buildx-action v4.0.0 -> v4.2.0 - docker/setup-qemu-action v4.0.0 -> v4.2.0 - actions/upload-artifact v7.0.0 -> v7.0.1 - actions/download-artifact v8.0.0 -> v8.0.1 main.yaml is left to #1196. Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
This was referenced Jul 14, 2026
linawolf
pushed a commit
that referenced
this pull request
Jul 25, 2026
Adds a `github-actions` package ecosystem to `dependabot.yml`, using the same schedule and conventions as the existing composer and npm entries (daily 16:00 Europe/Berlin, `[TASK]` prefix, `dependencies` + ecosystem label — the `github-actions` label has been created). ## Why Action versions in the workflows have only ever been updated by hand — `dependabot.yml` has covered composer and npm exclusively since it was created in #236, and the pins were last refreshed manually (#1194, then the #1184 → #1328/#1329 split). With this entry, Dependabot takes that over: it bumps SHA pins **and keeps the trailing `# vX.Y.Z` comments in sync** (see e.g. the actions bumps in TYPO3-Documentation/.github#19, same org). Minor/patch action bumps then flow through the existing auto-approve/auto-merge workflows like composer/npm updates already do; majors wait for review. ## Coordination - Trivial textual conflict with #1265, which also edits `dependabot.yml` (composer `ignore` key fix) — whichever lands second rebases. - Best merged after #1328/#1329 so Dependabot starts from current, annotated pins rather than re-proposing the same bumps. Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
Member
|
I think this will be superseeded by using depandabot? |
Contributor
Author
|
Think so ... |
Member
|
Letds close this PR and handle the depandabot updates step by step |
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
2 participants
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.
Second part of the #1184 split — version updates only, stacked on #1328 so this diff shows nothing but version changes. GitHub retargets it to
mainautomatically once #1328 merges (I'll rebase away the inherited commit then).Every new SHA was resolved and cross-checked against the GitHub API for its tag.
main.yamlis untouched (belongs to #1196) — note this leaves its threeactions/cachepins at v5.0.3 until #1196 lands.Per-action risk assessment
pull_request_target/workflow_runcontexts (#2454); ESM migrationpull_request_targetworkflow (pr-auto-merge.yaml) has no checkout step; all checkout usages run on push/tag/PR eventspath+keyusage insplit-repositories.yaml, no interface changeubuntu-latestprovides Node 24; thegithub-tokeninput andupdate-typeoutput we use are unchangedfrankdejonge/use-github-tokenanduse-subsplit-publishstay at 1.1.0 — that is their latest release. (Their Node 20 deprecation warning inPublish Sub-splitcannot be fixed by any bump; upstream has no Node 24 build yet.)Verification limits
PR CI cannot exercise most of these workflows:
docker.yaml,deploy-azure-assets.yamlrun on tag/release only;split-repositories.yamlon push tomain;docker-test.yamlonly onDockerfilechanges; the twopr-auto-*workflows on Dependabot PRs. First real exercise is the next release/tag and the next Dependabot PR.Follow-up worth considering (not in this PR): add a
github-actionsecosystem to.github/dependabot.ymlso these pins stay current automatically.