You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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...
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
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.
Description
Updated GitHub Action versions to v6 in multiple workflows to ensure compatibility with the latest GitHub Actions platform.
Requirements / Checklist
Issue number where discussion took place: #xxx
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/checkoutandactions/upload-artifactactions.What are the relevant tickets (if any)?
None applicable.
Screenshots (if appropriate or helpful)