ci: update actions in build pipeline - #113
Merged
Merged
Conversation
Signed-off-by: TTtie <me@tttie.cz>
applenick
approved these changes
Aug 2, 2026
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.
Updates the GitHub actions pipeline to move off of Node.js v20-based actions. Like with PGMDev/PGM#1708:
actions/setup-gradleat v5.0.2 was used instead of v6 for better caching without having to agree to a commercial licenseOn top of the above, full commit SHAs are used instead of version tags. This is a side-effect of me using pnpm to semi-automate the update1; I'm keeping it that way nevertheless as it's considered a good security practice to reduce supply chain attack risk.
Footnotes
I learnt about pnpm being able to update workflows sometime later after the PGM pull request was merged in, so tagged versions are being used there. Might update it over there as well at a later point. ↩