Skip to content

[ci] Bump outdated GitHub actions to current majors - #8336

Merged
TomasVotruba merged 1 commit into
mainfrom
deprecate-add-sensitive-parameter-attribute-rector
Aug 10, 2026
Merged

[ci] Bump outdated GitHub actions to current majors#8336
TomasVotruba merged 1 commit into
mainfrom
deprecate-add-sensitive-parameter-attribute-rector

Conversation

@TomasVotruba

Copy link
Copy Markdown
Member

Follow-up to #8335. Three actions were still on older majors, all now on the current one.

action before after
ramsey/composer-install v3 v4
stefanzweifel/git-auto-commit-action v5 v7
peter-evans/create-pull-request v6 v8

ramsey/composer-install@v4 was already used in every other workflow; claude_issue_fixer.yaml was the last v3 holdout.

Why the majors are safe here

git-auto-commit-action v5 -> v7. v6 removed create_branch, skip_checkout and skip_fetch, and v7 restored them; none of them are used here. Only commit_message, commit_author and commit_user_email are, and all three are unchanged. The branch input keeps the same default in both versions:

# v5 and v7 alike
branch:
    default: ${{ github.head_ref }}

That matters because rector.yaml and remove_unused_deps.yaml run on pull_request with a plain actions/checkout, so the repository is in detached HEAD. v7 notices this, but only logs a warning and carries on:

_check_if_repository_is_in_detached_state() {
    if [ -z "$(git symbolic-ref HEAD)" ]
    then
        _log "warning" "Repository is in a detached HEAD state. git-auto-commit will likely handle this automatically. [...]";

So [ci-review] Rector Rectify keeps working as before.

create-pull-request v6 -> v8. The v7 behaviour changes do not touch this usage:

  • git-token renamed to branch-token — this workflow passes token, not git-token
  • pull-request-operation now returns none instead of empty — the condition here is == 'created'
  • the deprecated PULL_REQUEST_NUMBER env output was removed — this workflow already reads the pull-request-number output

v8 only raises the self-hosted runner requirement to v2.327.1 for Node 24; these jobs run on ubuntu-latest.

Every workflow still parses as valid YAML.

Left alone, since they were not flagged and are not in the Node 20 group: dessant/lock-threads@v5, actions/stale@v10, crate-ci/typos@v1.46.0.

* ramsey/composer-install v3 -> v4, the version already used in every other workflow
* stefanzweifel/git-auto-commit-action v5 -> v7
* peter-evans/create-pull-request v6 -> v8

All inputs and outputs in use are unchanged across these majors.
@TomasVotruba
TomasVotruba force-pushed the deprecate-add-sensitive-parameter-attribute-rector branch from 15ea17c to 114a83d Compare August 10, 2026 17:27
@TomasVotruba
TomasVotruba enabled auto-merge (squash) August 10, 2026 17:28
@TomasVotruba
TomasVotruba disabled auto-merge August 10, 2026 17:28
@TomasVotruba
TomasVotruba merged commit 5f51f94 into main Aug 10, 2026
54 checks passed
@TomasVotruba
TomasVotruba deleted the deprecate-add-sensitive-parameter-attribute-rector branch August 10, 2026 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant