Add compile-time validation for runtime-import expressions#10312
Merged
Add compile-time validation for runtime-import expressions#10312
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
- Added extractRuntimeImportPaths() to extract file paths from runtime-import macros - Added validateRuntimeImportFiles() to validate expressions in imported files at compile time - Integrated validation into compiler workflow before code generation - Added comprehensive tests for path extraction, validation, and compiler integration - Validated manually with test workflows containing safe and unsafe expressions Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
- Changed assert.Error to require.Error for error assertions - Changed assert.NoError to require.NoError for success assertions Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add sanity validation for runtime-imports files
Add compile-time validation for runtime-import expressions
Jan 16, 2026
Contributor
|
@copilot merge main and handle the removal of @ syntax |
…ime-imports-files # Conflicts: # specs/artifacts.md
- Merged origin/main into branch - Removed @ inline syntax support from extractRuntimeImportPaths() - Removed all tests for @ inline syntax (@./path, @../path patterns) - Updated to align with main's removal of @ syntax in PR #10313 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
Author
This was referenced Jan 16, 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.
Runtime-import files were only validated at runtime, allowing workflows with invalid expressions to pass compilation and fail later during execution.
Changes
Expression validation (
pkg/workflow/expression_validation.go):extractRuntimeImportPaths()- Extracts file paths from{{#runtime-import filepath}}syntax, filtering out URLsvalidateRuntimeImportFiles()- Reads imported files and validates expressions against the allowed list at compile timeCompiler integration (
pkg/workflow/compiler.go):Test coverage (
pkg/workflow/runtime_import_validation_test.go):Example
With a shared file containing unsafe expressions:
<!-- .github/shared/instructions.md --> Token: ${{ secrets.GITHUB_TOKEN }} Runner: ${{ runner.os }}Compilation now fails early:
Previously this would compile successfully and fail at runtime.
Note: This PR only supports the
{{#runtime-import}}macro syntax. The@./pathinline syntax was removed from the main branch and is not supported.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.