Repository navigation
chore: upgrade actions to Node 24 runtime (SHA-pinned) #97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
John C. Bland II (johncblandii)
wants to merge
1
commit into
main
Choose a base branch
from
chore/node24-runtime-upgrade
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: cloudposse/terraform-provider-awsutils
Length of output: 17802
🌐 Web query:
Official actions/checkout documentation for persist-credentials default behavior and mszostok/codeowners-validator GitHub Action authentication and local Git usage💡 Result:
The actions/checkout GitHub Action and mszostok/codeowners-validator operate with distinct authentication and credential management behaviors. Actions/checkout persist-credentials Default Behavior By default, actions/checkout sets persist-credentials to true [1][2]. When enabled, this configuration persists the authentication token (or SSH key) used to clone the repository into the local Git configuration [1][3]. This allows subsequent Git commands in the same workflow job to run as the authenticated user without requiring manual token setup [1][4]. In recent versions, to improve security, the action stores these credentials in a separate file under the runner's temporary directory ($RUNNER_TEMP) rather than directly in the.git/config file, though the functional result remains that Git commands are automatically authenticated [1][3]. To disable this behavior and prevent the injection of credentials into the local environment, you can explicitly set persist-credentials: false in your workflow step [1][4]. mszostok/codeowners-validator Authentication and Usage The codeowners-validator functions as both a standalone CLI tool and a GitHub Action [5][6]. Its authentication requirements depend on the execution environment: GitHub Action Authentication: When running as a GitHub Action, the tool requires a GitHub token to perform API calls (e.g., checking if owners exist or are in an organization) [7][8]. You can provide this via a Personal Access Token (PAT) using the github_access_token input or by configuring a GitHub App using the github_app_id, github_app_installation_id, and github_app_private_key inputs [7][5]. Local Git Usage: When running locally, the tool is configured primarily via environment variables rather than direct integration with the local Git config [6][9]. To run locally, you must provide the repository path (often set via REPOSITORY_PATH) and authentication credentials—typically a GitHub token exported as the GITHUB_ACCESS_TOKEN environment variable [6][9]. The tool does not automatically leverage existing local Git credentials; instead, it relies on these explicitly provided environment variables to interface with the GitHub API [6][9].
Citations:
🏁 Script executed:
Repository: cloudposse/terraform-provider-awsutils
Length of output: 371
🏁 Script executed:
Repository: cloudposse/terraform-provider-awsutils
Length of output: 469
🏁 Script executed:
Repository: cloudposse/terraform-provider-awsutils
Length of output: 292
Disable checkout credential persistence.
actions/checkoutpersists credentials by default. This job runs third-party validator actions and no later Git command requires them. Setpersist-credentials: falseon the checkout step.🧰 Tools
🪛 zizmor (1.29.0)
[warning] 11-12: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
🤖 Prompt for AI Agents
Source: Linters/SAST tools