-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
ci(helm): roll prereleases on main pushes + manual trigger #3461
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
Merged
+59
−7
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
420aa12
ci(helm): roll prereleases on main pushes + manual trigger
nicktrn c44257d
chore(helm): add trailing newline to README to exercise prerelease wo…
nicktrn 5a9ba0e
ci(helm): harden manual dispatch + skip PR checks for helm-only changes
nicktrn bcf28dc
ci: drop ignore for old helm-pr-prerelease.yml (deleted in this PR)
nicktrn 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
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.
🟡 Script injection via direct interpolation of
github.ref_namein shell commandOn line 115,
${{ github.ref_name }}is directly interpolated into arun:shell script. GitHub Actions expands${{ }}expressions before the shell executes, so if the ref name contains shell metacharacters (e.g., backticks,$(), etc.), they will be interpreted by the shell. For example, a branch namedtest`malicious-command`would executemalicious-command. While this requires write access to the repo (to both create the branch and triggerworkflow_dispatch), it's a well-documented GitHub Actions script injection anti-pattern that could allow exfiltration of secrets available in the workflow (e.g.,GITHUB_TOKENwithpackages: write).Recommended fix: use an environment variable
Pass
github.ref_namevia an environment variable so the shell receives it as data rather than code:Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.