fix: allow expr || 'literal' default patterns in expression validation#19550
Merged
fix: allow expr || 'literal' default patterns in expression validation#19550
expr || 'literal' default patterns in expression validation#19550Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Allow expressions to utilize simple defaults
fix: allow Mar 4, 2026
expr || 'literal' default patterns in expression validation
Contributor
|
@copilot add more tests |
…ontext types) Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
Author
Added more tests in c3f87d4, covering:
Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
This was referenced Mar 4, 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
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.
Expression validation rejected valid default-value patterns like
${{ inputs.devices || 'mobile,tablet,desktop' }}because the parser correctly decomposed theOrNodeinto leaf nodes, then validated each leaf independently — causing string literals to fail the allowlist check.Changes
expression_validation.go: Add early-return literal check at the top ofvalidateSingleExpression— string ('...',"...",`...`), number, and boolean literals are unconditionally allowed since they are safe constantsexpression_validation.go: Promote the inline literal-detection regexes to pre-compiled package-level vars (stringLiteralRegex,numberLiteralRegex) used by both the new literal check and the existing OR fallback pathExample
These patterns now compile successfully:
Unauthorized left-hand sides are still rejected —
${{ secrets.TOKEN || 'fallback' }}continues to fail.Tests
Added comprehensive tests in
TestValidateExpressionSafetyWithParsercovering:|| 30), and boolean (|| false,|| true) literal defaultsinputs.*,github.event.inputs.*,github.*,steps.*,needs.*,env.*Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.