Skip to content

chore: Update outdated GitHub Actions versions - #1981

Merged
Finii merged 1 commit into
ryanoasis:masterfrom
pgoslatara:actup/update-actions-1769159579
Jan 26, 2026
Merged

Finii merged 1 commit into
ryanoasis:masterfrom
pgoslatara:actup/update-actions-1769159579

Conversation

@pgoslatara

Copy link
Copy Markdown
Contributor

Description

Updated GitHub Action versions to v6 in multiple workflows to ensure compatibility with the latest GitHub Actions platform.

Requirements / Checklist

  • Read the Contributing Guidelines
  • I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan.
    Issue number where discussion took place: #xxx
  • If this contains a font/glyph add its origin as background info below (e.g. URL)
  • Verified the license of any newly added font, glyph, or glyph set. License is: MIT (assuming standard license for GitHub Actions)

What does this PR do?

Updated GitHub Action versions in multiple workflows to v6, addressing outdated dependencies and ensuring compatibility with the latest GitHub Actions platform.

How should this be manually tested?

Will be tested in the CI pipeline of the pull request.

Any background context you can provide?

The update aligns with the latest GitHub Actions release, ensuring consistent behavior across workflows that use the actions/checkout and actions/upload-artifact actions.

What are the relevant tickets (if any)?

None applicable.

Screenshots (if appropriate or helpful)

@pgoslatara
pgoslatara marked this pull request as ready for review January 23, 2026 09:25
@Finii

Finii commented Jan 23, 2026

Copy link
Copy Markdown
Collaborator

Will be tested in the CI pipeline of the pull request.

Well, only the workflows that run an pulls will be tested.
For example we had a breaking change when updating upload-artifact from v3 to v4 (used in the release workflow)

to ensure compatibility with the latest GitHub Actions platform

To my understanding we do not need to update unless there is a warning (like we had in the past).
Of course updating is always good, but one needs to read the changelog closely, and not 'just try it out'. If the release breaks this means nightmare for me on release time. One release workflow runs several hours, so one should be certain it is ok...

@Finii

Finii commented Jan 26, 2026

Copy link
Copy Markdown
Collaborator

All actions we use, from->to:

actions/checkout@v4                                 6
actions/download-artifact@v4                        7 
actions/upload-artifact@v4                          6
dessant/lock-threads@v5                             6 
docker/build-push-action@v5                         6
docker/login-action@v3                             (3) 
docker/metadata-action@v5                          (5) 
docker/setup-buildx-action@v3                      (3) 
docker/setup-qemu-action@v3                        (3) 
EndBug/add-and-commit@v9                           (9) 
EndBug/latest-tag@v1                               (1) 
JamesIves/github-pages-deploy-action@v4            (4) 
softprops/action-gh-release@v2                     (2) 

@Finii
Finii merged commit cc7ffe4 into ryanoasis:master Jan 26, 2026
@Finii

Finii commented Jan 26, 2026

Copy link
Copy Markdown
Collaborator

Thanks for the PR!

@Finii

Finii commented Jan 26, 2026

Copy link
Copy Markdown
Collaborator

@allcontributors please add @pgoslatara for maintenance

@allcontributors

Copy link
Copy Markdown
Contributor

@Finii

I've put up a pull request to add @pgoslatara! 🎉

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.

2 participants