Update GitHub actions versions and add permissions - #795
Open
AerunDev wants to merge 3 commits into
Open
Conversation
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
1 participant
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.
Summary
This PR updates the GitHub Actions used by Pokémon Studio and tightens workflow permissions to follow current GitHub recommendations.
Changes
actions/checkout→v7actions/setup-node→v7actions/cache→v6actions/upload-artifact→v7contents: readcontents: writeonly to the production build job that needs to publish GitHub releases.Why
GitHub Actions have evolved significantly since the versions currently used by the project. Updating them keeps the CI compatible with current runners and supported action runtimes.
Explicit workflow permissions also reduce the privileges granted to CI jobs by default. Regular builds and pull requests only need read access, while write access is limited to the production publishing job.
This keeps the change intentionally small and focused on CI maintenance and repository security without changing the existing build or release workflow.